How to Configure MDB Message Redelivery When onMessage() Returns a Failure (Doc ID 1054218.1)

Last updated on FEBRUARY 14, 2025

Applies to:

Goal

Having a CMT message-driven bean, a J2EE application is deployed into 10.1.3 OC4J.
If an error is detected in the onMessage(), the application rolls backs the transaction (by calling   setRollbackOnly() method , or throws an ApplicationException message) :

In this case (transaction is rollback), after the onMessage() treatment, the message will be left in the JMS destination. And, OC4J will try automatically to re-deliver the message by re-calling the onMessage() method again.

This note demos how a message-driven bean can be configured to make OC4J re-attempt to deliver the message x number of times.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.