Redelivery limit not working for transaction timeout?

Question

hi,
          we have a redelivery limit on a queue that works, except for when there is a transaction timeout. in this case, the message seems to be redelivered infinitely. Is this a bug? a feature?
          we are using Weblogic Server 8.1 SP4. we don't have the source code, so i am not sure how the error handling is done or what exceptions are thrown.
          ------------------ejb-jar.xml------------
          <message-driven>
          <ejb-name>ImporFileReceiver</ejb-name>
          <ejb-class>au.com.auspost.pcms.common.integration.ejb.mdb.ImporFileReceiverMdb</ejb-class>
          <transaction-type>Container</transaction-type>
          <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
          <message-driven-destination>
          <destination-type>javax.jms.Queue</destination-type>
          <subscription-durability>NonDurable</subscription-durability>
          </message-driven-destination>
          </message-driven>
          <container-transaction>
          <method>
          <ejb-name>ImporFileReceiver</ejb-name>
          <method-intf>Local</method-intf>
          <method-name>onMessage</method-name>
          <method-params>
          <method-param>javax.jms.Message</method-param>
          </method-params>
          </method>
          <trans-attribute>NotSupported</trans-attribute>
          </container-transaction>
          <container-transaction>
          <method>
          <ejb-name>ImporFileReceiver</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>onMessage</method-name>
          <method-params>
          <method-param>javax.jms.Message</method-param>
          </method-params>
          </method>
          <trans-attribute>NotSupported</trans-attribute>
          </container-transaction>
          ------------------------ weblogic-ejb-jar.xml ---------
          <weblogic-enterprise-bean>
          <ejb-name>ImporFileReceiver</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>10</max-beans-in-free-pool>
          <initial-beans-in-free-pool>10</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>jms/pcmsImportFileQueue</destination-jndi-name>
          <connection-factory-jndi-name>jms/pcmsConnectionFactory</connection-factory-jndi-name>
          </message-driven-descriptor>
          <transaction-descriptor>
          <trans-timeout-seconds>3600</trans-timeout-seconds>
          </transaction-descriptor>
          <reference-descriptor>
          </reference-descriptor>
          <dispatch-policy>pcms.execute.queue.mdb.internal</dispatch-policy>
          <remote-client-timeout>0</remote-client-timeout>
          </weblogic-enterprise-bean>
          ------------------------ config.xml -----------------
          <JMSServer Name="eParcel JMS server"
          Store="eParcel JMS Server File Store" Targets="wls_pcms_prod1">
          <JMSQueue CreationTime="1190981682976"
          ErrorDestination="PCMS Import File Error Queue"
          JNDIName="jms/pcmsImportFileQueue"
          Name="PCMS Import File Queue" RedeliveryLimit="2"/>
          <JMSQueue CreationTime="1208347415759"
          JNDIName="jms/pcmsImportFileErrorQueue" Name="PCMS Import File Error Queue"/>
          </JMSServer>
          <JMSConnectionFactory JNDIName="jms/pcmsConnectionFactory"
          Name="eParcel JMS Connection Factory" Targets="wlc_pcms_prod"/>
          <JMSConnectionFactory JNDIName="jms/pcmsXAConnectionFactory"
          Name="eParcel JMS XA Connection Factory" Targets="wlc_pcms_prod" XAConnectionFactoryEnabled="true"/>
          -------------- weblogic log ---------------
          ####<24/04/2008 01:53:58 PM EST> <Warning> <EJB> <HX415> <wls_pcms_prod1> <ExecuteThread: '12' for queue: 'weblogic.kernel.Default'> <project_admin> <> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
          javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 3599 seconds
          Name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)],Xid=BEA1-696C9947A48195BA18DC(68926234),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3599,seconds left=60,activeThread=Thread[ExecuteThread: '12' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@447373e,re-Registered = false),SCInfo[wlsd_auspost_prod+wls_pcms_prod1]=(state=active),properties=({weblogic.transaction.name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)], weblogic.jdbc=t3://10.3.2.35:7003}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+, XAResources={JMS_eParcel JMS Server File Store, weblogic, wlsd_auspost_prod, com},NonXAResources={})],CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+)
          at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(I)V(ServerTransactionImpl.java:1614)
          at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Ljava/util/List;I)V(ServerTransactionManagerImpl.java:1117)
          at weblogic.transaction.internal.TransactionManagerImpl.wakeUp()V(TransactionManagerImpl.java:1881)
          at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp()V(ServerTransactionManagerImpl.java:1034)
          at weblogic.transaction.internal.WLSTimer.trigger(Lweblogic/time/common/Schedulable;)V(WLSTimer.java:31)
          at weblogic.time.common.internal.ScheduledTrigger.run()Ljava/lang/Object;(Optimized Method)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(Optimized Method)
          at weblogic.security.service.SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(SecurityManager.java:121)
          at weblogic.time.common.internal.ScheduledTrigger.executeLocally()V(ScheduledTrigger.java:229)
          at weblogic.time.common.internal.ScheduledTrigger.execute(Lweblogic/kernel/ExecuteThread;)V(ScheduledTrigger.java:223)
          at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)
          at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
          at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)
          ; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 3599 seconds
          Name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)],Xid=BEA1-696C9947A48195BA18DC(68926234),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3599,seconds left=60,activeThread=Thread[ExecuteThread: '12' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@447373e,re-Registered = false),SCInfo[wlsd_auspost_prod+wls_pcms_prod1]=(state=active),properties=({weblogic.transaction.name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)], weblogic.jdbc=t3://10.3.2.35:7003}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+, XAResources={JMS_eParcel JMS Server File Store, weblogic, wlsd_auspost_prod, com},NonXAResources={})],CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+).

Answer 1

Thanks Tom,
          Good point. The timeout exception is on ImportFileHandlerBean.handleMessage()....which is a session bean. The MDB must call this session bean, which also has a 3600 second timeout. It is confusing since the descriptor for the MDB has the transaction-timeout set, but i assume this is ignored for 'not-supported').
          I guess you would need to look at the code, but is there anyway a message go back on the queue, and not get the redelivery incremented?
          (I just had an evil thought...maybe the code could be physically sending the message onto the queue again when there is a timeout on the session bean.....hence would not get the redelivery incremented.....)
          -------------- ejb-jar.xml ----------------
          <session>
          <ejb-name>ImportFileHandler</ejb-name>
          <local-home>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerLocalHome</local-home>
          <local>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerLocal</local>
          <ejb-class>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean</ejb-class>
          <session-type>Stateless</session-type>
          <transaction-type>Container</transaction-type>
          </session>
          ----------- weblogic-ejb.jar.xml -----------
          <weblogic-enterprise-bean>
          <ejb-name>ImportFileHandler</ejb-name>
          <stateless-session-descriptor>
          </stateless-session-descriptor>
          <transaction-descriptor>
          <trans-timeout-seconds>3600</trans-timeout-seconds>
          </transaction-descriptor>
          <reference-descriptor>
          </reference-descriptor>
          <enable-call-by-reference>True</enable-call-by-reference>
          <local-jndi-name>ejb/ImportFileHandlerLocal</local-jndi-name>
          <remote-client-timeout>0</remote-client-timeout>
          </weblogic-enterprise-bean>