activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirby Frugia (JIRA)" <>
Subject [jira] Commented: (AMQ-724) Stomp client is not removed from the broker on client disconnect
Date Thu, 11 Dec 2008 16:49:05 GMT


Kirby Frugia commented on AMQ-724:

Ok.  It would be nice if this was documented in the activemq cpp documentation.  Other URI
options are documented.  I was looking for something like this, but was unaware this was an

> Stomp client is not removed from the broker on client disconnect
> ----------------------------------------------------------------
>                 Key: AMQ-724
>                 URL:
>             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,
> 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.

View raw message