Mr.Bish: Thanks for helping me using ActiveMQ these days. I turned off Inactivity monitor on the broker. I know it could kill old stale connections after a given time. However, I think why there is "old stale connections" in the first place is the real problem---If the client program and the broker disconnect TCP connections properly , there should never been old stale connections. I believe this phenomenon indicates there is some bugs in my client program, so I should found it. As for connection.close(), I did write codes to call close() and dispose() on connection, session and consumer. However, the program testers usually press F5 to run in debug mode and press shift+F5 to terminate the client program directly in visual studio 2010---normal dispose logic never get a chance to be runned in this situation and this could be the problem. I must find a way to fix this. There is one thing that still bothers me. Why activemq.log never logged anything about those "old stale connections" , neither their connection nor their disconnection ? Those properly behaving connections do have logs about their connection and disconnection.
-- View this message in context: http://activemq.2283324.n4.nabble.com/The-consumers-couldn-t-disconnect-from-broker-properly-tp4672722p4672737.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
