[
https://jira.jboss.org/browse/JBMESSAGING-1753?page=com.atlassian.jira.pl...
]
Howard Gao commented on JBMESSAGING-1753:
-----------------------------------------
In JBoss Messaging it has a deliveringCount to trace the number of messages being
delivered, but the messages are not traced. We can solve this issue by adding
"message id" into the deliveringCount maintenance code.
Please accommodate listInProcessMessages() to list all in process
messages to make JBM compatible with JBossMQ
--------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1753
URL:
https://jira.jboss.org/browse/JBMESSAGING-1753
Project: JBoss Messaging
Issue Type: Feature Request
Components: Configuration and Management
Affects Versions: 1.4.0.SP3.CP08
Environment: JBoss-EAP-4.3_CP6, JBM-1.4.0-SP3_CP8P1
Reporter: Tyronne Wickramarathne
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP11, 1.4.8.GA
It's not possible to view all "in process" messages via JMX console, but
this is possible on JBossMQ. Hence, customers migrating from JBossMQ to JBM encounters a
compatibility issue, porting/making their existing applications to work on JBM.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira