|
If you were logged in you would be able to see more operations.
|
|
|
Time Tracking:
Issue & Sub-Tasks
Issue Only
Issue & Sub-Tasks
Issue Only
|
|
|
|
File Attachments:
|
|
|
Image Attachments:
|
|
|
Environment:
|
Linux, Java 1.5.0_06
|
|
Issue Links:
|
Duplicate
|
|
|
|
dependent
|
|
|
|
This issue is depended upon by:
|
|
AMQ-1805
Persistent message leak when broker run out of disk space
|
|
|
|
|
AMQ-1067
Stomp consumer not removed if client does not send disconnect message.
|
|
|
|
|
|
|
|
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.
|
|
Description
|
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. |
Show » |
| No related reviews found.
|
|
Bug
Stomp client is not removed from the broker on client disconnect
