[
https://issues.apache.org/activemq/browse/AMQ-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies resolved AMQ-724.
----------------------------
Fix Version/s: 5.2.0
(was: 4.1.0)
(was: 4.0.2)
Resolution: Fixed
The associated patches no longer look valid for the current 5.2/trunk codebase.
You can on the broker url in the broker config to define options to directly
close the sockets - instead of using a separate thread in 5.2 -
e.g tcp://localhost:61616?socket.closeAsync=false
> 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
> Assignee: Rob Davies
> Fix For: 5.2.0
>
> Attachments: dumpemu4.png, patch.txt, patchInactivityMonitor.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.
