|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
5.4.2-fuse-01-00
|
|
Follow these steps to reproduce the problem:
- start broker
- start a producer and send two or more messages to a queue
- start jconsole
- click on the queue and select Operations.
- click browse and copy the JMSMessageID of the first message into clipboard
- invoke JMX operation removeMatchingMessages() with argument JMSMessageID='<message id>' , where <message id> is the copied JMSMessageID.
- verify that >= 1 message are still on the queue
- now start a consumer that connects to this queue. It won't get any messages.
|
|
Description
|
Follow these steps to reproduce the problem:
- start broker
- start a producer and send two or more messages to a queue
- start jconsole
- click on the queue and select Operations.
- click browse and copy the JMSMessageID of the first message into clipboard
- invoke JMX operation removeMatchingMessages() with argument JMSMessageID='<message id>' , where <message id> is the copied JMSMessageID.
- verify that >= 1 message are still on the queue
- now start a consumer that connects to this queue. It won't get any messages.
|
Show » |
|
Bug
Resolved
Critical
Consumers won't get msgs after JMX operation removeMatchingMessages() was called on a queue.
http://repo.fusesource.com/nexus/content/repositories/snapshots/org/apache/activemq/apache-activemq/5.4.2-fuse-SNAPSHOT/