This problem also exists in 4.0 Final. If Stomp client crashes (or disconnects unexpectedly) when there are unconsumed messages in the broker, something goes really wrong whith the broker. Broker shows warrnings that mbeans cannot be unregistered, messages got stuck in the queue (they cannot be consumed by other client) and broker's memory consumption increases. Broker needs to be restarted in such case.
Pleas someone take a look at that, because this problem really causes the pain to us and we cannot pass QA tests! -- View this message in context: http://www.nabble.com/Stomp+subscribtions+are+not+removed-t1627261.html#a4535714 Sent from the ActiveMQ - User forum at Nabble.com.
