]
Jeff Mesnil updated AS7-4960:
-----------------------------
Priority: Major (was: Minor)
JMS destinations' underlying core queues are not manageable
-----------------------------------------------------------
Key: AS7-4960
URL:
https://issues.jboss.org/browse/AS7-4960
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.2.Final (EAP)
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
When a JMS destination is created, we expose it in the management model (in jms-queue)
However, creating a JMS destination may also result in the creation of core-queues
resources (1 for JMS queues, 1 per subscribers for JMS topics). This core queues are not
exposed in the management model. Only those configured in config files or CLI are
present.
(However we make sure that we add core _addresses_ (1 for each JMS destination) at
runtime to the management model)
This means that AS7 messaging subsystem is not a "correct" reflection of the
HornetQ runtime. I can't make my mind whether it is a problem. Afaict, most operations
on these underlying queues can be also done at the JMS destination level through their
management operations.
--
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: