Sachin, I think you can change the transaction timeout in the jboss conf.... figure out a maximum time for message processing and increase the timeout accordingly...
hth dim ----- Original Message ----- From: "Sachin Pandey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 27, 2002 4:41 PM Subject: Re: Handling RuntimeExceptions in MDB > Thanks all for the input on my problem. At times I get a > javax.ejb.TransactionRolledbackLocalException from the container as the > message processing takes a long time. I really can't protect against this as > it essentially depends on the incoming message. From what I understand since > this exception is thrown container won't receive an acknowledgement for the > message and try and redeliver it? I am right about this? If that's the case > should I put an explicit check in the onMessage() to check if the message > has been redelivered via the JMS API. I am using JBoss 2.4.4 > > Thanks again. > Cheers > Sachin Pandey > NUIX Pty Ltd > Level 8, 143 York Street, > Sydney 2000 > Phone: (02) 92839010 > Fax: (02) 92839020 > > Disclaimer: > This message is intended only for the named recipient. If you are not the > intended recipient you are notified that disclosing,copying, distributing or > taking any action in reliance on the contents of this information is > strictly prohibited. > ----- Original Message ----- > From: "Dmitri Colebatch" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, September 27, 2002 6:38 AM > Subject: Re: Handling RuntimeExceptions in MDB > > > > > > So should I catch RuntimeExceptions explicitly in my > > > > onMessage() implementation. The MDB is using container > > > > managed transaction. > > > > > > Yes. And then you can publish the error on a specialized Topic, where > > > it could be treated. > > > > > > Also, JMS implementations usually feature a "retry count" or "poisoned > > > message" feature, you might want to look into that if this suggestion > > > won't work for you. > > > > JBoss has a DLQ and a configurable retry I believe.... have a look at your > > container configuration. > > > > cheers > > dim > > > > > =========================================================================== > > To unsubscribe, send email to [EMAIL PROTECTED] and include in the > body > > of the message "signoff EJB-INTEREST". For general help, send email to > > [EMAIL PROTECTED] and include in the body of the message "help". > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
