[
https://issues.apache.org/jira/browse/CXF-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-1609.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0.7
> The setSynchronousTimeout on the ClientImpl does not prevent reading the
> socket to timeout...
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-1609
> URL: https://issues.apache.org/jira/browse/CXF-1609
> Project: CXF
> Issue Type: Bug
> Components: Configuration, Core
> Affects Versions: 2.1.1
> Reporter: Benjamin Coiffe
> Fix For: 2.1.1, 2.0.7
>
>
> This method has apparently been replaced with
> HTTPConduit.setReceiverTimeout(Long).
> HTTPConduit.setConnectionTimeout(Long)
> I can't remember how the old way was meant to work (private void
> ClientImpl.waitForResponse(...)) but this seems to be deprecated atm.
> Other thing:
> HTTPConduit.setReceiverTimeout(Long)
> HTTPConduit.setConnectionTimeout(Long)
> are casted as int in the conduit :
>
> connection.setConnectTimeout((int)clientSidePolicy.getConnectionTimeout());
> connection.setReadTimeout((int)clientSidePolicy.getReceiveTimeout());
> This conversion is very dangerous e.g Long.MAX_VALUE is converted into a
> negative integer!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
