activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Kruthoff (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (AMQ-1067) Stomp consumer not removed if client does not send disconnect message.
Date Fri, 01 Jun 2007 08:53:33 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andreas Kruthoff reopened AMQ-1067:
-----------------------------------


This issue is not yet resolved on 4.1.1, 4.1.1-SNAPSHOT, or 4.1.0. It can be reproduced very
easily with the provided perl script. Ticket https://issues.apache.org/activemq/browse/AMQ-724
describes the same problem but with a c client.

ActiveMQ-4.0.2 works fine, so the error was introduced in version 4.1.


> Stomp consumer not removed if client does not send disconnect message.
> ----------------------------------------------------------------------
>
>                 Key: AMQ-1067
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1067
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.1.0
>         Environment: Solaris 10, Perl 5.8.4
>            Reporter: Chris Knight
>            Priority: Critical
>             Fix For: 4.1.1, 4.2.0
>
>         Attachments: perl.tar.gz
>
>
> Run "clearQueue.pl TEST.QUEUE"
> Check in jconsole. The client will still be marked as active even when the script is
killed. This prevents any meaningful use of queues if any consumption is done via stomp.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message