Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-1609

The setSynchronousTimeout on the ClientImpl does not prevent reading the socket to timeout...

    XMLWordPrintableJSON

    Details

    • 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
    • Labels:
      None
    • Estimated Complexity:
      Moderate

      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!

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              benjamin coiffe Benjamin Coiffe
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: