Thanks for the reply. I have spent more time on this and think it is to do with the PDUReaderworker in SMPPSession. When a session is created it constructs a thread pool on readers.
In some cases these threads are not being destroyed when the session is closed after each attempt to reconnect. I suspect this is due to some conflict on a synchronised method within the JSMPP library so the threads simply remain. This just builds up because the SMPPProducer keeps trying to reconnect. I think it is becase we try and establish more than one connection and so get this conflict. I am not sure that there is much that can be done in camel, because it is lower down in the jsmpp library. regards Antony -- View this message in context: http://camel.465427.n5.nabble.com/Unreleased-thread-possible-in-SMPP-component-tp4922901p4944732.html Sent from the Camel - Users mailing list archive at Nabble.com.
