Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# JMS Template --> Configuration --> Redelivery

Tasks Related Topics Attributes

## Overview

This tab defines configuration redelivery attributes for a JMS template, which provides an efficient means of defining multiple destinations with similar attribute settings.

The configurable redelivery attributes for a JMS template are the same as those configured for a destination. However, if the destination that is using a JMS template specifies a message redelivery value for an attribute, that redelivery value is used.

## Tasks

Creating a JMS Template

## Related Topics

"WebLogic JMS Fundamentals" in Programming WebLogic JMS

"Managing WebLogic JMS" in Programming WebLogic JMS

"Developing a WebLogic JMS Application" in Programming WebLogic JMS

## Attributes

Table 23-1

Attribute Label | Description | Value Constraints
--- | --- | ---
Redelivery Delay Override | The delay, in milliseconds, before rolled back or recovered messages are redelivered, regardless of the RedeliveryDelay 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 RedeliveryDelay 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. JMSTemplateMBean` Attribute: `RedeliveryDelayOverride` | Minimum: -1 Maximum: 9223372036854775807 Default: -1 Dynamic: yes
Redelivery Limit | The number of redelivery tries a message can have before it is moved to the Error Destination specified on this page. This setting overrides any redelivery limit set by the message sender. If the redelivery limit is configured, but no error destination is configured, then persistent and non-persistent messages are simply dropped (deleted) when they reach their redelivery limit. The default value (-1) specifies that the destination will not override the message sender's redelivery limit setting. 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. This means that after a restart, the number of delivery attempts on each message is reset to zero. MBean: `weblogic.management. configuration. JMSTemplateMBean` 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. 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 quotas. This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean: `weblogic.management. configuration. JMSTemplateMBean` Attribute: `ErrorDestination` | Minimum: -1 Default: null Dynamic: yes