JDBC MultiPools

This tab defines message redelivery configuration attributes for a JMS topic. After defining a JMS server, you can configure its topics. You can configure one or more topics for each JMS server.

Note: You configure destinations explicitly or by configuring a JMS template that can be used to define multiple destinations with similar attribute settings, as described in JMS Template Tasks.

Table 0-9

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 RedeliveryDelayOverride 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 tries a message can have before it is moved to the error destination. 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. JMSTopicMBean Attribute: RedeliveryLimit	Minimum: -1 Maximum: 2147483647 Default: -1 Dynamic: yes
Error Destination	The name of the target error destination for messages that have reached their redelivery limit. If no error destination is configured, 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: The error destination must be a destination that is configured on the local JMS server. This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean: weblogic.management. configuration. JMSTopicMBean Attribute: ErrorDestination	Default: null Dynamic: yes

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 RedeliveryDelayOverride 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 tries a message can have before it is moved to the error destination. 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.
JMSTopicMBean

Attribute: RedeliveryLimit

Minimum: -1

Maximum: 2147483647

Default: -1

Dynamic: yes

Error Destination

The name of the target error destination for messages that have reached their redelivery limit. If no error destination is configured, 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: The error destination must be a destination that is configured on the local JMS server.

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

MBean: weblogic.management.
configuration.
JMSTopicMBean

Attribute: ErrorDestination

Default: null

Dynamic: yes