The number of redelivery attempts a message can make before it is moved to the error destination specified on this page. However, if a redelivery limit is set without an error destination, then persistent and non-persistent messages are silently deleted when they reach their redelivery limit, and no exception is thrown. This setting overrides any redelivery limit set by the message producer.
Note: The redelivery limit with no error destination behavior also applies to transactional messages, which are not rolled back for future redelivery and no exception is thrown.
The default value (-1) specifies that the destination will not override the message sender's redelivery limit setting.
When the value is set to zero, messages are received at-most once. No redelivery attempts are made in the event of a rollback or receive. Instead, messages are either moved to the configured error destination or are simply deleted.
This attribute is dynamically configurable, but only incoming messages are impacted; previously sent messages continue to use their original redelivery limit.
Note: The number of times a message has been redelivered is not persisted. Therefore, after a server restart, the number of delivery attempts on each message is reset to zero.
MBean: weblogic.management. configuration. JMSTopicMBean
Attribute: RedeliveryLimit
|