JMS Topic --> Configuration --> Redelivery

Redelivery Delay Override

The delay, in milliseconds, before rolled back or recovered messages are redelivered, regardless of the Redelivery Delay specified by the consumer and/or connection factory. Redelivered queue messages are put back into their originating destination; redelivered topic messages are put back into their originating subscription.

The default value (-1) specifies that the destination will not override the Redelivery Delay setting.

This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.

Note: Changing the Redelivery Delay Override only affects future rollbacks and recovers, it does not affect rollbacks and recovers that have already occurred.

MBean: weblogic.management.
configuration.
JMSTopicMBean

Attribute: RedeliveryDelayOverride

Minimum: -1

Maximum: 9223372036854775807

Default: -1

Dynamic: yes

Redelivery Limit

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

Minimum: -1

Maximum: 2147483647

Default: -1

Dynamic: yes

Error Destination

The name of the target destination (queue or topic) for messages that have reached their redelivery limit. If no error destination is configured on the local JMS server, then such messages are simply dropped. If a message has expired and the Expiration Policy is set to Redirect, then the message is moved to the specified error destination.

If this destination has a template, the none option indicates that the error destination comes from the template. If this destination does have a template, none indicates that there is no error destination configured.

Note: Configured destination quotas do not apply to expired or redelivery limit messages that are redirected to an error destination. Such messages are still moved into an error destination even if that destination has reached its quota.

This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.

MBean: weblogic.management.
configuration.
JMSTopicMBean

Attribute: ErrorDestination

Minimum: -1

Default: null

Dynamic: yes