[CXF-7818] HTTPConduit - timeout ignore when using dispatch as client

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 3.2.4
• Component/s: JAX-WS Runtime
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: boonhock
• Created: 09/Aug/18 22:45
• Updated: 18/Sep/23 18:49
• Resolved: 10/Sep/18 06:55

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);