bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

JMS Queue --> Configuration --> Redelivery

Tasks Additional Documentation Attributes

Overview

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

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

Tasks

Create a JMS Queue

Clone a JMS Queue

Delete a JMS Queue

Additional Documentation

(Requires an Internet connection.)

"Managing JMS"in the Administration Guide

"WebLogic JMS Fundamentals" in Programming WebLogic JMS

"Managing WebLogic JMS" in Programming WebLogic JMS

"Developing a WebLogic JMS Application"in Programming WebLogic JMS

Attributes

Attribute Label | Description | Value Constraints
--- | --- | ---
Redelivery Delay Override | The RedeliveryDelayOverride value in milliseconds before rolled back and recovered messages are redelivered. Defines the delay, in milliseconds, before rolled back or recovered messages are redelivered, regardless of the RedeliveryDelay specified by the consumer and/or connection factory. 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. MBean: weblogic.management. configuration. JMSQueueMBean Attribute: RedeliveryDelayOverride | Minimum: -1 Maximum: 9223372036854775807 Default: -1 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Redelivery Limit | The number of redelivery tries a message can have before it is placed in the error destination. Depending on whether an error destination is configured, the following occurs when the redelivery limit is reached: If no error destination is configured, or the quota for the error destination would be exceeded, then persistent and non-persistent messages are simply dropped. If an error destination is configured and the error destination is at quota, then an error message is logged and the message is dropped. However, if the message is persistent, it remains in the persistent store. This ensures that a persistent message will be redelivered when WebLogic Server is rebooted. The default value (-1) specifies that the destination will not override the RedeliveryLimit setting. This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. Note:Changing the RedeliveryLimit does not affect messages that have already reached this limit. The next time such messages are redelivered, they will immediately be redirected to the error destination. The number of times of 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. JMSQueueMBean Attribute: RedeliveryLimit | Minimum: -1 Maximum: 9223372036854775807 Default: -1 Configurable: yes Dynamic: yes Readable: yes Writable: 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. 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. JMSQueueMBean Attribute: ErrorDestination | Default: null Dynamic: yes