CXF JAXRS client not reusing TCP connections?

I would definitely try updating to a newer and supported version of CXF. There have been a LOT of updates to the JAX-RS stuff in the newer versions of CXF and this issue may already be fixed.

I would love to, but I'm stuck with this version at present due to some much wider project dependencies outside of my control. :-( – John Rix Jul 11 at 16:29 Dan, I tried the upgrade to 2.4.1 on my development machine but experienced the same problem unfortunately. – John Rix Jul 12 at 9:10.

In your sample code you get a JAX-RS Response, which getEntity() method will return an InputStream by default. Therefore, being CXF not responsible for consuming the stream, this is obviously left open. If you don't explicitly close that, it would be closed during a Garbage Collection phase.

But even so, under high traffic rates, this little latency prevents the underlying HTTP connection to be reinserted into the internal pool of persistent connections exploited by HttpURLConnection (that CXF is using under the bonnet). So it cannot be reused on time. If you take care of closing the InputStream, you should not see a large number of TIME_WAIT sockets anymore.

Thanks agoware, that makes sense. In the interim, I ended up degrading to a basic commons Http connection based approach, since my requests were simple to formulate and I had little need to actually do anything with the response. If I use CXF again though, this will definitely be useful!

– John Rix Oct 4 at 9:04.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.