[ https://issues.apache.org/activemq/browse/AMQ-724?page=comments#action_37176 ] Chris Ochs commented on AMQ-724: --------------------------------
This is not fixed as of 4.0.2 RC4, or at least there is another bug with the exact same behavior. Wasn't hard to duplicate either, just kill a stomp connection while it's reading and bam, phantom consumer. > Stomp client is not removed from the broker on client disconnect > ---------------------------------------------------------------- > > Key: AMQ-724 > URL: https://issues.apache.org/activemq/browse/AMQ-724 > Project: ActiveMQ > Issue Type: Bug > Components: Transport > Affects Versions: 4.0 > Environment: Linux, Java 1.5.0_06 > Reporter: Danielius Jurna > Assigned To: james strachan > Fix For: 4.0.2, 4.1 > > Attachments: StompSubscriptionRemoveTest.java > > > If Stomp client crashes (or disconnects unexpectedly) when there are > unconsumed messages in the broker, the subscriptions are not removed from the > broker and some phantom consumer is still consuming messages. If you connect > other client, it receives only half messages (other half messages goes to > that phantom consumer still left afrter client disconnect). There are no > error logs in activemq logs. We are using stomp client, whith client > acknowledge mode, so on broker restart, all messages are delivered properly. > You can also see in jmx console, that subscription still exists whithout any > connection left. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
