configuring DLQ issues

[brooney]

Hey there,

i'm having trouble with JBoss 4.0.1sp1 and the JBoss MQ DLQ failover. i've got a queue configured as shown below in the jbossmq-destinations-service.xml file and the jboss-service.xml file has the DLQ defined. however, when a message is not able to be processed, it gets added back the queue as expected but the RedeliverLimit seems to be ignored and stays on the queue forever until i manually remove it from the queue.

am i missing some configuration here to force it to go to the DLQ after 3 retries?

jbossmq-destinations-service.xml:

<server>
 <mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=myQueue">
 <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
 <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
 <attribute name="MessageCounterHistoryDayLimit">-1</attribute>
 <attribute name="RedeliveryLimit">3</attribute>
 <attribute name="RedeliveryDelay">180000</attribute> <!-- 30 min -->
 <attribute name="SecurityConf">
 <security>
 <role name="guest" read="true" write="true" />
 </security>
 </attribute>
 </mbean>

jboss-service.xml

 <!-- ==================================================================== -->
 <!-- System Destinations -->
 <!-- ==================================================================== -->

 <!-- Dead Letter Queue -->
 <mbean code="org.jboss.mq.server.jmx.Queue"
 name="jboss.mq.destination:service=Queue,name=DLQ">
 <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
 <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
 </mbean>

thanks
ben

[kungfoo]

bump

[kungfoo]

myabe my question should be 'does the jms consumer need to be a mdb for the dlq functionality to work'? this doesn't make much sense to me as that would limit the use of configuring a DLQ but thought i may ask it

does my jms code need to do something special for the DLQ to be used? my code currently doesn't do much other than throw an exception when the process has failed.

btw kungFOO = brooney :)

[brooney]

bump :(

[genman]

Are you using an MDB? What do the debug logs say?

[kungfoo]

i'm not using a MDB. we have a custom client that listens to the queue and consumes messages when they arrive. so i don't think log file will be of help.

[genman]

A DLQ is an MDB-specific feature. You can emulate it, though. Take a look at the JBoss source.

[kungfoo]

thanks for the feedback. this is what i was starting to believe but couldn't find confirmation on it.

i will take a look at my options.

[jaikiran]

One of the options might be to follow the approach of using a monitor, which has been mentioned at:

http://wiki.jboss.org/wiki/Wiki.jsp?page=DeadLetterQueues

Here's an extract:

If you don't want to write an MDB, you can just install a monitor that fires a notification everytime the queue size changes.