[
https://issues.apache.org/jira/browse/AMQ-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arvydas Jonusonis updated AMQ-5010:
-----------------------------------
Description:
To reproduce:
1) create queue named "A"
2) send test message to A (verify queue A contains a message via Web Console or
"activemq-admin browse" command.
3) create queue named "A." (if you check the contents of A. they are identical
to that of A)
4) delete queue A.
5) check queue A
Despite a positive pending message count, no messages appear in queue A when
looking via web console or activemq-admin tool. They do, however, show up via
JMX operations on the queue, such as browseAsTable().
was:
To reproduce:
1) create queue named "A"
2) send test message to A (verify queue A contains a message via Web Console or
"activemq-admin browse" command.
3) create queue named "A."
4) delete queue A.
5) check queue A
Despite a positive pending message count, no messages appear in queue A when
looking via web console or activemq-admin tool. They do, however, show up via
JMX operations on the queue, such as browseAsTable().
> deleting queue suffixed with a dot (".") causes messages to disappear in
> similarly named queue (without the dot)
> ----------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-5010
> URL: https://issues.apache.org/jira/browse/AMQ-5010
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.7.0, 5.9.0
> Reporter: Arvydas Jonusonis
>
> To reproduce:
> 1) create queue named "A"
> 2) send test message to A (verify queue A contains a message via Web Console
> or "activemq-admin browse" command.
> 3) create queue named "A." (if you check the contents of A. they are
> identical to that of A)
> 4) delete queue A.
> 5) check queue A
> Despite a positive pending message count, no messages appear in queue A when
> looking via web console or activemq-admin tool. They do, however, show up via
> JMX operations on the queue, such as browseAsTable().
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)