Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure JMS template message delivery failure parameters

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

To configure message redelivery options for a JMS template:

  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 template resource that you want to configure:
  3. Click the Configuration > Delivery Failure tab.
  4. On the 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 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, select a pre-configured queue or topic destination for messages that have reached their redelivery limit, or for expired messages when the Expiration Policy is set to Redirect. The error destination must be configured on the same JMS server targeted by the destination for which it is defined. If no error destination is configured, then undeliverable messages are simply deleted.

    For more information about these fields, see Configuration Options.

  5. Save your changes:
  6. 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