[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1374:
-----------------------------------------
Same thing happens with ExpiryQueue. If in the destinations-service.xml a destination
mbean uses a DLQ or ExpiryQueue whose mbean element appears after it, it won't get the
DLQ/ExpiryQueue reference during service start, even though the DLQ/ExpiryQueue is
eventually started up. When the user tries to send the message, the server session
consumer endpoint will try to get the DLQ/ExpiryQueue ref from the destination, which in
that case is null, then the consumer endpoint will use default DLQ/ExpiryQueue instead.
However user can still see the correct DLQ/ExpiryQueue name from jmx console, that's
because the DLQ's ObjectName is in the destination service, and by clicking apply
button on the console will update the DLQ correctly. So the next consumer creation will
cause the right DLQ to be used.
We need to use a facility class to solve the dependency issue during the destination
service start stages, set them correctly if such cases happens.
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
--
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