[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1374) DLQ override depends on the queues definition order.

[Howard Gao (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12430968#action_12430968 ] 

Howard Gao commented on JBMESSAGING-1374:
-----------------------------------------

Further investigation on the reason why <depends> doesn't work:

- <depends> only affect the service start sequence, not the mbean load sequence. The loading of mbeans should be in the order of that specified in the deploy config file.
- The original setDLQ() happens during the mbean loading(creation) time, which will try to resolve the DLQ by JMXAccessor.getJMXAttributeOverSecurity(...) method. If at that time the DLQ mbean service is not loaded (created), it simply gets null. 
- the setDLQ() then is never called again during the rest of the server startup process. Only if the user change it from the jmx console, it'll be changed.
- adding a setDLQ() at service start time can guarantee all the mbeans are created, so we won't get null DLQ any more, and the real DLQ will be used instead of the default one.
- same reason stays with the ExpiryQueue case.


> 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: Howard Gao
>             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