OTN Home > Oracle WebLogic Server 12.1.2.0 Documentation > Administration Console Online Help > Configure queue message delivery failure options

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure queue message delivery failure options


After you create a queue, you can change the default message delivery failure values, like defining a message redelivery limit, selecting a message expiration policy, and specifying an error destination for expired or undeliverable messages.

To configure message delivery failure options for a queue:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the Administration Console, navigate to the queue resource that you want to configure:
  3. On the Configuration: Delivery Failure page:
    1. In Redelivery Delay Override, specify the delay before rolled back or recovered messages are redelivered, regardless of the Redelivery Delay specified by the consumer and/or connection factory.
    2. In Redelivery Limit, specify the number of redelivery tries a message can have before it is moved to an error destination.
    3. In Expiration Policy, select the expiration policy (Discard, Log, or Redirect) used when an expired or undeliverable message is encountered on a destination.
    4. In Expiration Logging Policy, if Log is the selected Expiration Policy, specify what information about the message that you want to be logged.
    5. In Error Destination, when the Expiration Policy is set to Redirect, select a pre-configured destination to receive messages that have expired or reached their redelivery limit. The error destination must be targeted to the same JMS server as the destinations for which the error destination is defined. If no error destination is configured, then expired or undeliverable messages are simply deleted.

    For more information about these fields, see Configuration Options.

  4. Save your changes:
  5. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

Back to Top