[
https://issues.apache.org/jira/browse/CXF-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863146#comment-16863146
]
Aritz Bastida commented on CXF-7112:
------------------------------------
Hi! Is this issue really fixed? I'm experiencing exactly this problem.
My "receiveTimeout" configuration was working OK in the sync version, but is
now ignored when I switched to async bindings...
> 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)