[CXF-1609] The setSynchronousTimeout on the ClientImpl does not prevent reading the socket to timeout...

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.1
• Fix Version/s: 2.1.1, 2.0.7
• Component/s: Configuration, Core
• Estimated Complexity: Moderate
• Assignee: Unassigned
• Reporter: Benjamin Coiffe
• Created: 26/May/08 10:18
• Updated: 03/Jul/08 17:19
• Resolved: 16/Jun/08 17:46

Description

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!