apache cxf could not send message and read time out

Question

What might be the cause of:

org.apache.cxf.interceptor.Fault: Could not send Message.

Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking https://xxx.xxx.xxx.xxx:8443/services/test: Read timed out

It usually occurs after I send a soap request to the ws. I'm using apache cxf. I'm completely sure that the ws is up and running because before the time out occur the client will send 2 more request. The timeout happens in the third soap request.

score 17 · Answer 1 · edited Dec 04 '21 at 10:14

I have encountered this error as well for my webservice client. The solution that worked for me is to configure the http client in the CXF config file (cxf.xml).

As documented in Apache CXF document:

1.Add the http-conduit namespace and xsd:

<beans ...
       xmlns:http-conf="http://cxf.apache.org/transports/http/configuration
       ...
       xsi:schemaLocation="...
           http://cxf.apache.org/transports/http/configuration
           http://cxf.apache.org/schemas/configuration/http-conf.xsd
       ...">

2.Add the http-conduit tag/element and set the ReceiveTimeout/ConnectionTimeout to 300000 ms:

<http-conf:conduit name="*.http-conduit">
      <http-conf:client 
                      ConnectionTimeout="300000"
                      ReceiveTimeout="300000"/>       
</http-conf:conduit>

score 14 · Answer 2 · answered Feb 01 '13 at 09:12

The error message means that your web service client was trying to receive data from a remote web service over the network, but no data was received for a specific period of time, so the web service client stopped waiting for the data to be received.

One of the possible causes might be that the timeout property is too low. Defaults to cxf default values of 30000 and 60000 ms respectively. These can be changed depending how you are creating your client.

If you are creating a client using java code you can use:

//1 minute for connection
((BindingProvider) wsPort).getRequestContext().put("com.sun.xml.ws.connect.timeout", 1 * 60 * 1000); 

//3 minutes for request
((BindingProvider) wsPort).getRequestContext().put("com.sun.xml.ws.request.timeout", 3 * 60 * 1000);

If you are using Spring, you can use a map like this:

<util:map id="jaxwsProperties">
    <entry key="com.sun.xml.internal.ws.request.timeout">
        <value type="java.lang.Integer">120000</value>
    </entry>
    <entry key="com.sun.xml.internal.ws.connect.timeout">
        <value type="java.lang.Integer">60000</value>
    </entry>
</util:map>

Then set that map into your <jaxws:client.../> configuration.

okay ill try that :) anyway can wrong soap request format can also the culprit of the error??,, i accidentally sent a soap request with null values/ "" values then i suddenly received the ws soap response .. — irumi, Feb 01 '13 at 16:21
The properties have changed names to `javax.xml.ws.client.connectionTimeout` and `javax.xml.ws.client.receiveTimeout` respectively. — Anders R. Bystrup, Aug 16 '16 at 09:13
The use of `BindingProviderProperties.CONNECT_TIMEOUT`and `BindingProviderProperties.REQUEST_TIMEOUT`as keys should prevent problems of name change. — Manur, Dec 13 '19 at 09:37
@Manur this class is deprecated and it points to old property names — Kirill, Apr 08 '21 at 10:13

score 4 · Answer 3 · answered May 02 '17 at 13:22

Another approche to config timeouts (programmatically):

JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
Object serviceClass = factory.create();
defineTimeouts(serviceClass);

static void defineTimeouts(Object serviceClass) {
    Client cxfClient = ClientProxy.getClient(serviceClass);
    HTTPConduit httpConduit = (HTTPConduit) cxfClient.getConduit();

    HTTPClientPolicy httpClientPolicy = new HTTPClientPolicy();
    httpClientPolicy.setConnectionTimeout(DEFAULT_CLIENT_CONNECTION_TIMEOUT);
    httpClientPolicy.setReceiveTimeout(DEFAULT_CLIENT_RECEIVE_TIMEOUT);
    httpConduit.setClient(httpClientPolicy);
}

score 0 · Answer 4 · edited May 23 '17 at 10:31

You might want to change the receiveTimeout setting from Apache CXF src and replace the existing cxf-rt-transports-http-version.jar in your server.

Brief instructions: (Got the instructions from Wildfly 8.2/undertow read time out)

Download CXF2.7.16 src from apache
Add maven/bin to PATH
Export MAVEN_OPTS=-Xmx512m to fix permgen errors
Open ./rt/transports/http/src/main/resources/schemas/wsdl/http-conf.xsd and change ReceiveTimeout from 60000 to whatever needed for eg. 600000 (10 minutes)
Run mvn -Pfastinstall
Get the "patched" cxf-rt-transports-http-2.7.16.jar from ./rt/transports/http/target folder
Replace cxf-rt-transports-http-2.7.16.jar in your server. For example, with wildfly8.2, it is in .//modules/system/layers/base/org/apache/cxf/impl/main folder and remember to update module.xml inside the same folder to use this patched cxf-rt-transports-http-2.7.16.jar.

This should resolve the SocketTimeoutException caused by the underlying Apache CXF used in the server.

apache cxf could not send message and read time out

4 Answers4