Tuning Active Message Expiration Configuring a JMS Server to Actively Scan Destinations for Expired Messages

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

Use the Active Expiration feature to define the timeliness in which expired messages are removed from the destination to which they were sent or published. Messages are not necessarily removed from the system at their expiration time, but they are removed within a user-defined number of seconds. The smaller the window, the closer the message removal is to the actual expiration time.

14.14.8 Configuring a JMS Server to Actively Scan Destinations for Expired Messages

Follow these directions to define how often a JMS server will actively scan its destinations for expired messages. The default value is 30 seconds, which means the JMS server waits 30 seconds between each scan interval. 1. Follow the directions for navigating to the JMS Server: Configuration: General page of the Administration Console in Configure general JMS server properties in the Oracle WebLogic Server Administration Console Help. 2. In the Scan Expiration Interval field, enter the amount of time, in seconds, that you want the JMS server to pause between its cycles of scanning its destinations for expired messages to process. To disable active scanning, enter a value of 0 seconds. Expired messages are passively removed from the system as they are discovered. For more information about the Expiration Scan Interval attribute, see JMS Server: Configuration: General in the Oracle WebLogic Server Administration Console Help. 3. Click Save. There are a number of design choices that impact performance of JMS applications. Some others include reliability, scalability, manageability, monitoring, user transactions, message driven bean support, and integration with an application server. In addition, there are WebLogic JMS extensions and features have a direct impact on performance. For more information on designing your applications for JMS, see Best Practices for Application Design in Programming JMS for Oracle WebLogic Server. 14-20 Performance and Tuning for Oracle WebLogic Server

14.15 Tuning Applications Using Unit-of-Order