[
https://issues.apache.org/jira/browse/CXF-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863362#comment-16863362
]
Freeman Fang edited comment on CXF-7112 at 6/13/19 8:53 PM:
------------------------------------------------------------
Hi [~Aritz],
No worries, I saw this problem, it's because you use
"javax.xml.ws.client.receiveTimeout" property which is ignored by
AsyncHttpConduit, working on a fix.
And the workaround so far is that you put the receiveTimeout on HttpClientPolicy
code like
{code}
HTTPConduit c = (HTTPConduit)ClientProxy.getClient(g).getConduit();
c.getClient().setReceiveTimeout(3000);
{code}
Freeman
was (Author: ffang):
Hi [~Aritz],
No worries, I saw this problem, it's because you use
"javax.xml.ws.client.receiveTimeout" property which is ignored by
AsyncHttpConduit, working on a fix.
Freeman
> 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)
