[
https://issues.apache.org/activemq/browse/AMQ-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ronner updated AMQ-724:
------------------------------
Attachment: StompScriptNoDisconnect.txt
StompScriptComplete.txt
That's how you can reproduce it:
{{$ netcat -v -c localhost 61613 < StompScriptComplete.txt}}
*CONNECT*, *SEND* a message and *DISCONNECT* properly.
{{$ netcat -v -c localhost 61613 < StompScriptNoDisconnect.txt}}
*CONNECT*, *SEND* a message and closes the connection {color:red}without{color}
*DISCONNECT*.
> 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.0
>
> Attachments: dumpemu4.png, patch.txt, SessionState.patch,
> StompScriptComplete.txt, StompScriptNoDisconnect.txt,
> 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.
-
You can reply to this email to add a comment to the issue online.
