[
https://jira.jboss.org/jira/browse/JBMESSAGING-1729?page=com.atlassian.ji...
]
Ondrej Žižka updated JBMESSAGING-1729:
--------------------------------------
Summary: JMS Topic::listAllMessages JMX operation returns empty list. (was: JMS
Topic::List All Messages - empty table is displayed, as there were no messages.)
Description:
SSIA . Rep. steps:
1) Create a topic (MyTopic)
2) Send few durable messages to it (Ejb3TestApps can be used)
3) Find the "name=MyTopic,service=Topic" Mbean
5) Ensure that messages count is not zero
4) Perform the listAllMessages operation
5) See that the result is an empty list.
Tested with EAP 5 CR3, "all" config, default DB (HSQL)
was:
SSIA . Rep. steps:
1) Create a topic
2) Send few messages to it (Ejb3TestApps can be used)
3) Ensure that metrics show non-zero messages count
4) Perform the List All Messages operation
5) As the result, see the table with no messages.
(This might be a duplicate jira issue, but I didn't find any similar.)
JMS Topic::listAllMessages JMX operation returns empty list.
------------------------------------------------------------
Key: JBMESSAGING-1729
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1729
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.4.GA
Reporter: Ondrej Žižka
Assignee: Charles Crouch
SSIA . Rep. steps:
1) Create a topic (MyTopic)
2) Send few durable messages to it (Ejb3TestApps can be used)
3) Find the "name=MyTopic,service=Topic" Mbean
5) Ensure that messages count is not zero
4) Perform the listAllMessages operation
5) See that the result is an empty list.
Tested with EAP 5 CR3, "all" config, default DB (HSQL)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira