Re: redelivery limit not working for transaction timeout?

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.ImportFileHandlerLo
calHome</local-home>
     
<local>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerLocal&l
t;/local>
     
<ejb-class>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBea
n</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>