Specification equivalent of DLQ

[cluck]

JBoss implements a DLQ for messages that exceded the retry threshhold, which is very useful behaviour in our app. I was just curious if the J2EE spec. includes something similar? I can't see anything, but I may be missing something...

[adrian.brock]

It is not in the spec, but most JMSs have it.

Regards,
Adrian

[cluck]

Thats what I thought - pity, it is very useful behaviour but I can't use it an keep our app portable.

[nlmarco]

Hello *!

How can I replace the DLQ by another queue for one MDB? I tried to add the following into the jboss.xml of my deployed module, but it had NO effect:

<container-configurations>
 <container-configuration>
 <!-- Use the standardjboss.xml container-name so we only have
 to specify the elements we want to override -->
 <container-name>Standard Message Driven Bean</container-name>
 <container-invoker-conf>
 <MDBConfig>
 <ReconnectIntervalSec>30</ReconnectIntervalSec>
 <DLQConfig>
 <DestinationQueue>queue/my/FailQueue</DestinationQueue>
 <MaxTimesRedelivered>3</MaxTimesRedelivered>
 <TimeToLive>0</TimeToLive>
 </DLQConfig>
 </MDBConfig>
 </container-invoker-conf>
 </container-configuration>
</container-configurations>

What am I doing wrong?

I either need to define this on a per-queue-basis or on a per-MDB-basis. To set the redeliveryDelay and redeliveryLimit on a per-queue-basis (in the xxx-service.xml) works fine, but how can I overwrite the "queue/DLQ" coming from standardjboss.xml?

Best regards, Marco :-)

[nlmarco]

"cluck" wrote:
Thats what I thought - pity, it is very useful behaviour but I can't use it an keep our app portable.

As most of the J2EE implementations have it, why not rely on it being existent and just make configurable in your app what queue it is? We do it this way - hence our app is maybe not running on all J2EE servers but at least on all interesting ones.