Defining an Expiration Logging Policy Expiration Log Output Format

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 . 4. Click Save.

14.14.5 Defining an Expiration Logging Policy

The following section provides information on the expiration policy. The Expiration Logging Policy parameter has been deprecated in this release of WebLogic Server. In its place, Oracle recommends using the Message Life Cycle Logging feature, which provide a more comprehensive view of the basic events that JMS messages will traverse through once they are accepted by a JMS server, including detailed message expiration data. For more information about message life cycle logging options, see Message Life Cycle Logging in Configuring and Managing JMS for Oracle WebLogic Server. For example, you could specify one of the following values: ■ JMSPriority, Name, Address, City, State, Zip ■ header, Name, Address, City, State, Zip ■ JMSCorrelationID, properties The JMSMessageID field is always logged and cannot be turned off. Therefore, if the Expiration Policy is not defined that is, none or is defined as an empty string, then the output to the log file contains only the JMSMessageID of the message.

14.14.6 Expiration Log Output Format

When an expired message is logged, the text portion of the message not including timestamps, severity, thread information, security identity, etc. conforms to the following format: ExpiredJMSMessage JMSMessageId=MESSAGEID HeaderFields Field1=Value1 [Field2=Value2] … ] UserProperties Property1=Value1 [Property=Value2] … ] ExpiredJMSMessage where MESSAGEID is the exact string returned by Message.getJMSMessageID. For example: ExpiredJMSMessage JMSMessageID=ID:P851839.1022176920343.0 HeaderFields JMSPriority=7 JMSRedelivered=false UserProperties Make=Honda Model=Civic Color=WhiteWeight=2680 ExpiredJMSMessage If no header fields are displayed, the line for header fields is not be displayed. If no user properties are displayed, that line is not be displayed. If there are no header fields and no properties, the closing ExpiredJMSMessage tag is not necessary as the opening tag can be terminated with a closing bracket . Tuning WebLogic JMS 14-19 For example: ExpiredJMSMessage JMSMessageID=ID:N223476.1022177121567.1 All values are delimited with double quotes. All string values are limited to 32 characters in length. Requested fields andor properties that do not exist are not displayed. Requested fields andor properties that exist but have no value a null value are displayed as null without single quotes. Requested fields andor properties that are empty strings are displayed as a pair of single quotes with no space between them. For example: ExpiredJMSMessage JMSMessageID=ID:N851839.1022176920344.0 UserProperties First=Any string longer than 32 char ... Second=null Third= ExpiredJMSMessage

14.14.7 Tuning Active Message Expiration