Glad you found the problem. The answer to your question about the behavior if the TCP connection is broken is that yes, I believe that will cause a cleanup. But keep in mind that hard-killing a process with an open TCP connection doesn't result in the connection closing till the OS times it out, so depending on how you do the close, there might be a delay before it happens (and a reconnect attempt before the timeout happens might or might not prevent the cleanup from happening). I haven't tested this, so if it's something you're concerned about, I recommend you test it out to be sure it does what you expect (and then report back to let us know what you found).
Tim On Tue, Jul 19, 2016 at 6:45 PM, RuralHunter <ruralhun...@gmail.com> wrote: > We'v found the leaking client by checking the producer count of the queues > one by one in JConsole. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Producer-count-keeps-increasing-tp4714087p4714138.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
