Tuning WebLogic JMS 14-17
3.
If you selected the Log expiration policy in previous step, use the Expiration Logging Policy field to define what information about the message is logged.
For more information about valid Expiration Logging Policy values, see Section 14.14.5, Defining an Expiration Logging Policy
.
4.
Click Save.
14.14.3 Configuring an Expiration Policy on Queues
Follow these directions if you are configuring an expiration policy on queues without using a JMS template. Expiration policies that are set on specific queues will override
the settings defined on a JMS template.
1.
Follow the directions for navigating to the JMS Queue: Configuration: Delivery Failure page in Configure queue message delivery failure options in the Oracle
WebLogic Server Administration Console Help.
2.
From the Expiration Policy list box, select an expiration policy option.
■
Discard — Expired messages are removed from the system. The removal is not logged and the message is not redirected to another location.
■
Log — Removes expired messages from the queue and writes an entry to the server log file indicating that the messages were removed from the system.
You define the actual information that will be logged in the Expiration Logging Policy field described in the next step.
■
Redirect — Moves expired messages from the queue and into the Error Destination defined for the queue.
■
For more information about the Expiration Policy options for a queue, see JMS Queue: Configuration: Delivery Failure in the Oracle WebLogic Server
Administration Console Help.
3.
If you selected the Log expiration policy in the previous step, use the Expiration Logging Policy field to define what information about the message is logged.
For more information about valid Expiration Logging Policy values, see Section 14.14.5, Defining an Expiration Logging Policy
.
4.
Click Save
14.14.4 Configuring an Expiration Policy on Templates
Since JMS templates provide an efficient way to define multiple destinations topics or queues with similar attribute settings, you can configure a message expiration policy
on an existing template or templates for your destinations.
1.
Follow the directions for navigating to the JMS Template: Configuration: Delivery Failure page in Configure JMS template message delivery failure options in the
Oracle WebLogic Server Administration Console Help.
2.
In the Expiration Policy list box, select an expiration policy option.
■
Discard — Expired messages are removed from the messaging system. The removal is not logged and the message is not redirected to another location.
■
Log — Removes expired messages and writes an entry to the server log file indicating that the messages were removed from the system. The actual
information that is logged is defined by the Expiration Logging Policy field described in the next step.
14-18 Performance and Tuning for Oracle WebLogic Server
■
Redirect — Moves expired messages from their current location into the Error Destination defined for the destination.
■
For more information about the Expiration Policy options for a template, see JMS Template: Configuration: Delivery Failure in the Oracle WebLogic Server
Administration Console Help.
3.
If you selected the Log expiration policy in Step 4, use the Expiration Logging Policy field to define what information about the message is logged.
For more information about valid Expiration Logging Policy values, see Section 14.14.5, Defining an Expiration Logging Policy
