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

HTTPConduit - timeout ignore when using dispatch as client

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: 3.2.4
    • Fix Version/s: None
    • Component/s: JAX-WS Runtime
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      Hi  All, I am using org.apache.cxf.transport.http.HTTPConduit as HTTP session and javax.xml.ws.Dispatch as client. I am trying to set connection timeout to 10 minutes so that it is still alive after it received the response (persistent connection). However, the second message do not use the same connection as the first one.

      After the first message end, if I execute it to send second SOAP message between 4 seconds, it is still using the same connection.

      Thus, I would like to ask am I missing something here?

       

      Code:

      Client client = ((DispatchImpl) dispatch).getClient();
      HTTPConduit conduit = (HTTPConduit) client.getConduit();

      TLSClientParameters tlsClientParameters = new TLSClientParameters();
      tlsClientParameters.setSSLSocketFactory(socketFactory);
      tlsClientParameters.setDisableCNCheck(true);
      conduit.setTlsClientParameters(tlsClientParameters);

      conduit.getClient().setConnection(ConnectionType.KEEP_ALIVE);
      conduit.getClient().setConnectionTimeout(600000);
      conduit.getClient().setAllowChunking(false);
      conduit.getClient().setReceiveTimeout(600000);

      SOAPMessage response = dispatch.invoke(requestSource);

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              obl0702 boonhock
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 48h
                48h
                Remaining:
                Remaining Estimate - 48h
                48h
                Logged:
                Time Spent - Not Specified
                Not Specified