DLQ override depends on the queues definition order.

[szhigunov]

I set DLQ for MyQ to MyDLQ.

The queues are defined in destinations-service.xml.

If MyDLQ is defined before MyQ, everything works fine.

But if MyDLQ is defined after MyQ, the behavior is confusing.
1) Server starts up without errors.
2) MyQ MBean shows MyDLQ as the value of DLQ attribute.
3) But failed message gets sent to the default DLQ destination.
4) If I execute "Apply Changes" on MyQ MBean (without changing the attributes), it fixes the problem,
and next failed message goes to MyDLQ.

If it is not a bug, I think it worth to mention in the user guide that queue and DLQ have to be defined in the correct order.

[timfox]

http://jira.jboss.org/jira/browse/JBMESSAGING-1374

[timfox]

If you want to make sure one service gets started before another using standard JBoss MBean config, you just need to add an explicit dependency, otherwise beans will get started in order they are in the file.

See JBoss as documentation for more info.