[ 
https://issues.apache.org/jira/browse/CXF-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864032#comment-16864032
 ] 

Aritz Bastida edited comment on CXF-7112 at 6/14/19 12:58 PM:
--------------------------------------------------------------

Thank you very much for the fix, and also for the workaround. :)

By the way, in case you have some time to look at it, some months ago I opened 
a related issue reporting other conformance errors with the JAX-WS spec: 
CXF-7951
 * CXF does not return a Response Bean wrapping all out parameters, as required 
by the spec section 2.3.4.3.
 * CXF does not wrap exceptions with WebServiceException, as required by the 
spec section 4.3.3.

 


was (Author: aritz):
Thank you very much for the fix, and also for the workaround. :)

By the way, in case you have some time to look at it, some months ago I opened 
a related issue reporting other conformance errors with the JAX-WS spec: 
[CXF-7951|https://issues.apache.org/jira/browse/CXF-7951]
 * It does not return a Response Bean wrapping all out parameters, as required 
by the spec section 2.3.4.3.
 * It does not wrap exceptions with WebServiceException, as required by the 
spec section 4.3.3.

 

> AsyncHTTPConduit ignore the ReceiveTimeout when use Async JAXWS api
> -------------------------------------------------------------------
>
>                 Key: CXF-7112
>                 URL: https://issues.apache.org/jira/browse/CXF-7112
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>            Priority: Major
>             Fix For: 3.1.9, 3.2.0
>
>
> As for the ahc we should use the application level way to check the 
> ReceiveTimeout to let ahc connectionManager to manage the connection 
> lifecycle for a better performance.
> This works with jaxws sync api and AsyncHTTPConduit.getHttpResponse have this 
> timeout check(AsyncHTTPConduitTest.testTimeout cover this scenario), but with 
> jaxws async api we don't have this timeout check for ahc, we need provide one



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to