History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: AMQ-1067
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Hiram Chirino
Reporter: Chris Knight
Votes: 1
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
ActiveMQ

Stomp consumer not removed if client does not send disconnect message.

Created: 21/Nov/06 02:48 PM   Updated: 22/Oct/07 01:37 PM
Component/s: Broker
Affects Version/s: 4.1.0
Fix Version/s: 5.0.0, 4.1.2

Time Tracking:
Not Specified

File Attachments:
  Size
GZip Archive perl.tar.gz 2006-11-21 02:48 PM Chris Knight 4 kb
Environment: Solaris 10, Perl 5.8.4
Issue Links:
Duplicate
 
dependent
 


 Description  « Hide
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.

 All   Comments   Work Log   Change History   Subversion Commits   FishEye   Crucible      Sort Order: Ascending order - Click to sort in descending order
Chris Knight - 21/Nov/06 02:51 PM
To recreate the problem:
clearQueue.pl <TEST_QUEUE>
Ctrl^C

You'll then find that the consumer is still active according to the broker.


Chris Knight - 21/Nov/06 02:56 PM
This only affects version 4.1.0. 4.0.1 is fine.

Andreas Kruthoff - 01/Jun/07 01:53 AM
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.


Rob Davies - 19/Aug/07 10:24 PM
I think this is fixed ?

Andreas Kruthoff - 20/Aug/07 12:45 AM
Version 4.0 is fine, 4.1 doesn't work, stomp consumer isn't removed.

Hiram Chirino - 22/Oct/07 01:37 PM
Fixed in the upcoming 4.1.2 and 5.0.0 releases.