[
https://issues.apache.org/jira/browse/CXF-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760010#action_12760010
]
Dennis Kieselhorst commented on CXF-2036:
-----------------------------------------
http://www.nabble.com/Re%3A-Retry-on-java.net.SocketTimeoutException%3A-Read-timed-out-p21979671.html
-->
This MAY already be doable today with the ConduitSelector stuff and the
Failover strategy things built into the clients. They already detect IO Errors
and allow touch points to select a new conduit and retry.
Take a look at the code in cxf-rt-core/org.apache.cxf.clustering. Most likely,
you would just need a FailoverStrategy that would always return the same
Endpoint.
--
Daniel Kulp
<--
> Add option to retry a http request on socket error to http client
> -----------------------------------------------------------------
>
> Key: CXF-2036
> URL: https://issues.apache.org/jira/browse/CXF-2036
> Project: CXF
> Issue Type: New Feature
> Components: Transports
> Affects Versions: 2.1.4
> Reporter: Dennis Kieselhorst
> Attachments: cxf-2036.patch
>
>
> See
> http://www.nabble.com/Retry-on-java.net.SocketTimeoutException%3A-Read-timed-out-td21939913.html
> The client gets 'java.net.SocketTimeoutException: Read timed out' because the
> remote server is currently busy or 'java.net.SocketException: Connection
> reset' because of a network issue.
> A new option in the http client configuration can catch these errors for a
> number of times and only throws the exception, if retry was not successful.
> <http-conf:conduit
> name="{http://apache.org/hello_world_soap_http}SoapPort.http-conduit";>
> <http-conf:client RetryOnSocketError="2" />
> </http-conf:conduit>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
