This week's book giveaway is in the Jobs Discussion forum. We're giving away four copies of Developer Career Masterplan: Build your path to senior level and beyond with practical insights from industry experts and have Heather VanCura and Bruno Souza on-line! See this thread for details.
Originally posted by Rafael Rocha: hi. i have a doubt about when one MDB is not redelivered and redelivered with sucess? wich all cases possible?
yeah, the message will not be redeliverd because the MDB did not throw any exception.
edited: compelemt for read specification above:
As per section 220.127.116.11 of EJB 3.0 Core specification: A transaction must be started before the dequeuing of the JMS message and, hence, before the invocation of the message-driven bean�s onMessage method.
The resource manager associated with the arriving message is enlisted with the transaction as well as all the resource managers accessed by the onMessage method within the transaction.
If the onMessage method invokes other enterprise beans, the container passes the transaction context with the invocation. The transaction is committed when the onMessage method has completed.
If the onMessage method does not successfully complete or the transaction is rolled back, message redelivery semantics apply. [ July 30, 2008: Message edited by: Rafael Rocha ]