8 Replies Latest reply on Oct 16, 2006 3:01 AM by jaikiran pai

    configuring DLQ issues

    ben rooney Newbie

      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