If I run with the AMQ broker on one machine and the producer&consumer on a second machine then all the TIME_WAIT sockets are on the AMQ machine (from localhost, to localhost). So, I'm pretty convinced the cause is there. Also, if I remove all camel logic and just produce and consume on the same queue, there are no TIME_WAIT sockets (or very few).
The number of sockets is certainly increasing - I'm pushing through around 100 msg/s and seeing around 100 TIME_WAIT sockets appearing per second. Interestingly the number continues to rise for "a while" after I kill the producer - my assumption is that it is because camel hasn't got through them all yet. The number of TIME_WAIT sockets stops rising a few seconds after I kill off the producer. Here's my http://www.nabble.com/file/p16131500/activemq.xml activemq.xml . My camel config is all right at the end. Other than that, the only bit I've deliberately changed is to trim down the network connectors section. -Dominic -- View this message in context: http://www.nabble.com/Getting-lots-of-TIME_WAIT-sockets-tp16119896s22882p16131500.html Sent from the Camel - Users mailing list archive at Nabble.com.
