[
https://issues.jboss.org/browse/AS7-5807?page=com.atlassian.jira.plugin.s...
]
Tomaz Cerar commented on AS7-5807:
----------------------------------
Can you verify this is still true for 7.2.x nightly builds? There was lots of changes
& fixes in management for messaging subsystem.
Jboss AS7 - JMS Topic Metrics inconsistency
--------------------------------------------
Key: AS7-5807
URL:
https://issues.jboss.org/browse/AS7-5807
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.2.Final (EAP)
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