As I investigate: it doesn't look like we specify any keepalive parameters in our configuration (either the xml configuration, wsdl or Java code).
Does anyone know if the default keepalive behavior changed between 2.2.10 and 2.7.8? -----Original Message----- From: Warren, Jared S [mailto:[email protected]] Sent: Wednesday, July 30, 2014 12:40 PM To: [email protected] Subject: Connection reuse change in 2.7.8? Hey all - We recently deployed a package that included several library upgrades, including an update from CXF 2.2.10 to 2.7.8 (it also included a migration from one application container to another - so there is quite a lot of noise in the system in terms of changes). In this case, CXF is the consumer of a SOAP service hosted on another platform. Nothing has changed wrt the service provider. After the upgrade deployment, we started seeing relatively frequent "javax.xml.ws.WebServiceException: Could not send Message" exceptions with a root cause of "Caused by: java.net.SocketTimeoutException: Read time out after xyz millis". When we revert our deployment to the 2.2.10-based release, the problem goes away. When we performed a network trace to watch what's happening, we can see that the client is reusing the same TCP/IP connection for multiple requests (a good thing). After many uses over a period of time, the service provider stack sends a FIN. The client (CXF) continues attempting to send requests despite the FIN. The service provider sends a RESET for each of those attempts. Eventually, CXF times out and throws the exception above to the client code. When we run the same trace on the 2.2.10 based infrastructure, we do not see any TCP/IP connection reuse. I'm off to read CXF connection reuse documentation, but I thought I'd ask here first, "Any suggestions on a fix?" Thanks jared The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If the reader of this message is not the intended recipient, you are hereby notified that your access is unauthorized, and any review, dissemination, distribution or copying of this message including any attachments is strictly prohibited. If you are not the intended recipient, please contact the sender and delete the material from any computer. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If the reader of this message is not the intended recipient, you are hereby notified that your access is unauthorized, and any review, dissemination, distribution or copying of this message including any attachments is strictly prohibited. If you are not the intended recipient, please contact the sender and delete the material from any computer.
