[
https://issues.apache.org/jira/browse/CXF-6224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296583#comment-14296583
]
DESA commented on CXF-6224:
---------------------------
our architecture is based 3 tiers. It consists of a Mobile client, middleware
and SI. Communication between the middleware and the SI is done with webService
SOAP. Our test is to simulate call 500 for 30 seconds. The case observed is
that the customer has timeout but of the webservice call continues for a
considerable time.
With this parameter Execute Async Timeout, if the call is made after 60
seconds, the call should not be abandoned?
> HttpAsyncClient with async calls: the soap call are late
> ----------------------------------------------------------
>
> Key: CXF-6224
> URL: https://issues.apache.org/jira/browse/CXF-6224
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.7.14
> Reporter: DESA
> Priority: Critical
> Fix For: NeedMoreInfo
>
>
> After migration to 2.7.14 CXF library, we saw that the soap call are late.
> The call to service remained active for 5 minutes although no call was made
> during those 5 minutes.
> It cause server freeze.
> <http:conduit name="*.http-conduit">
> <http:client AutoRedirect="true" Connection="Keep-Alive"
> ConnectionTimeout="#{ 60* 1000 }"
> ReceiveTimeout="#{ 60 * 1000 }"
> AsyncExecuteTimeout="#{ 60 * 1000 }"
> AsyncExecuteTimeoutRejection="true"
> />
> </http:conduit>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
