[
https://jira.jboss.org/jira/browse/JBMESSAGING-1729?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1729:
-----------------------------------------
This is expected behavior.
The reason you can list the messages because the messages are being delivered to the
subscriber side. Unless you close the connection or the session.
The amount of messages that JBM delivered to a consumer in one batch is controlled by
PrefetchSize attribute of connection factory. default is 150. It can be set to as small as
1.
Using default 150 value, the first time you need to send more than 200 messages to be able
to see something returned by listAllMessages() if the consumer (subscriber)'s session
and/or connection keeps open.
I'll close this issue by rejecting it.
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: Howard Gao
Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1, 1.4.7.GA
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
4) Ensure that messages count is not zero
5) Perform the listAllMessages operation
6) 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