[jboss-jira] [JBoss JIRA] (WFLY-965) JMS Topic Metrics Inconsistency
[
https://issues.jboss.org/browse/WFLY-965?page=com.atlassian.jira.plugin.s...
]
Clebert Suconic commented on WFLY-965:
--------------------------------------
The semantic of the method is return the sum of messages for the durable subscriptions..
not the count of durable messages.
We don't make a distinction of durable messages and non durable messages beyond they
won't survive a restart.
So, I would say this is behaving as planned.
What is the usecase where you would need to make a distinction between durable and non
durable messages on the counters?
JMS Topic Metrics Inconsistency
-------------------------------
Key: WFLY-965
URL: https://issues.jboss.org/browse/WFLY-965
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS
Reporter: Florin Slev
Assignee: Jeff Mesnil
Jboss AS7 - JMS Topic Metrics inconsistency
Have Jboss AS7 7.1.2 installed with Hornetq implementation.
Steps:
1.) Create a jms topic inside the standalone.xml configuration.
For e.g. "TestTopic".
In HornetQ translation this means a core address named: "jms.topic.TestTopic".
2.) Using HornetQ Core Client create some durable subscriptions for that topic.
HornetQ translation: core queues (subscriptions) bounded to the core address
"jms.topic.TestTopic".
3.) Create some messages using the HornetQ ClientMessage.
4.) Set the messages as NOT durable (message.setDurable(false)) and send them to the
topic.
Actual:
Inside the Jboss AS7 http-management interface, from the browser, inside the jms
destionations page you will see the previously sent messages as durable. Which is false.
If you restart the server, they will be deleted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira