JMS Delivery Failure - "Redirect" Expiration Policy Not Working
(Doc ID 2636159.1)
Last updated on MARCH 26, 2021
Applies to:Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
The expectation is that if the consumer end system is down or not reachable even after multiple retries, the jms message should rollback to the error destination JMS queue.
user needs to configure the expiration policy "Redirect" so that the message is delivered to the error queue instead of staying in recovery state.
If no error destination is configured, then such messages are simply dropped. If a message has expired or reached its redelivery limit, and the Expiration Policy is set to Redirect, then the message is moved to the specified Error Destination.
For standalone destinations, an error destination must be another standalone destination that is targeted to the same JMS server as the destinations for which the error destination is defined.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document