Administration Console Online Help
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.
"WebLogic JMS Fundamentals" in Programming WebLogic JMS
"Managing WebLogic JMS" in Programming WebLogic JMS
"Developing a WebLogic JMS Application" in Programming WebLogic JMS
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 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.
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.
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 not 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 quotas.