[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] Updated: (AMQ-724) Stomp client is not removed from the
From:       "Danielius Jurna (JIRA)" <jira () apache ! org>
Date:       2006-05-29 0:18:51
Message-ID: 13919949.1148861931523.JavaMail.jira () brutus
[Download RAW message or body]

     [ https://issues.apache.org/activemq/browse/AMQ-724?page=all ]

Danielius Jurna updated AMQ-724:
--------------------------------

    Attachment: StompSubscriptionRemoveTest.java

TestCase which shows this bug - takes time to complete.


> 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
> Type: Bug

> Components: Transport
> Versions: 4.0
> Environment: Linux, Java 1.5.0_06
> Reporter: Danielius Jurna
> 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


[prev in list] [next in list] [prev in thread] [next in thread]