5 Replies Latest reply on Jul 29, 2009 7:00 AM by Mariusz Smykula

    MaxDeliveryAttempts not working

    Mariusz Smykula Newbie

      MaxDeliveryAttempts value defined is destinations-services for my Queue is not working. I have MaxDeliveryAttempts=1000000 but there is in logs

      2009-07-27 11:46:52,735 252490342 WARN
      [org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler]
      (WorkManager(2)-60:) Message redelivered=11 max=10 sending it to the dlq delegator->JBossMessage[20458449768469361]:PERSISTENT, deliveryId=11

      Im using JBM 1.4.1.GA (JBoss 5.0.1)

        • 1. Re: MaxDeliveryAttempts not working
          Andy Taylor Master

          From the log message it looks like its the JCA layer thats sending to the DLQ not JBM. You're MDB config is probably incorrect.

          The JCA or App server forums should be able to help you or take a look at the MDB docs.

          • 2. Re: MaxDeliveryAttempts not working
            Mariusz Smykula Newbie

             

            "ataylor" wrote:
            From the log message it looks like its the JCA layer thats sending to the DLQ not JBM. You're MDB config is probably incorrect.

            The JCA or App server forums should be able to help you or take a look at the MDB docs.

            Im using default configuration, so the default configuration in jboss501 is not working?
            <mbean code="org.jboss.jms.server.destination.QueueService"
             name="jboss.messaging.destination:service=Queue,name=MyQueue"
             xmbean-dd="xmdesc/Queue-xmbean.xml">
            
             <attribute name="MessageCounterHistoryDayLimit">-1</attribute>
            
             <attribute name="RedeliveryDelay">300000</attribute>
            
             <attribute name="MaxDeliveryAttempts">100000</attribute>
            
             <attribute name="SecurityConfig">
             <security>
             <role name="myrole" read="true" write="true" create="true" />
             </security>
             </attribute>
             <depends optional-attribute-name="ServerPeer">
             jboss.messaging:service=ServerPeer</depends>
             <depends>jboss.messaging:service=PostOffice
             </depends>
             <attribute name="Clustered">true</attribute>
             </mbean>


            • 3. Re: MaxDeliveryAttempts not working
              Mariusz Smykula Newbie

              The documentations simple say:

              5.6.2.1.6. MaxDeliveryAttempts

              The maximum number of times delivery of a message will be attempted before sending the message to the DLQ, if configured. If set to -1 (the default), the value from the ServerPeer config is used. Any other setting overrides the value set on the ServerPeer config.


              Setting DefaultMaxDeliveryAttempts in ServerPeer configuration to high value also not work.

              • 4. Re: MaxDeliveryAttempts not working
                Andy Taylor Master

                Yeah, thats part of the messaging docs. But MDB's do there own DLQ handling which has nothing to do with messaging. I think its a setting on the MDB but i am not sure.

                • 5. Re: MaxDeliveryAttempts not working
                  Mariusz Smykula Newbie

                  Ok, thanks. I think I should use MaxTimesRedelivered in standardjboss.xml.