Slow performance when a WebSphere Application Server V5 application sends a message to a queue
 Technote (troubleshooting)
 
Problem(Abstract)
You may notice slow performance when an application running on WebSphere® Application Server V5 sends a message to a queue or publishes a message to a topic using JMS.
 
Cause
The slow performance may be caused by the use of persistent messages. By default, messages that are sent to a queue or topic from an application running in WebSphere Application Server will be non-persistent. However, this behavior can be changed by modifying the Persistence property for the JMS destination in the Administrative Console. If this was changed to Persistent or if it is set to Application Defined and the application specifies persistent messages, then slower than expected performance may occur.
Persistent messages are written to a log before they arrive on a queue. Non-persistent messages are not logged. The disk I/O that is necessary for persistent messages causes slower performance.
 
Resolving the problem
To improve the performance, use non-persistent messages. The performance will improve as messages will not be written to the disk when they are sent.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Message Service (JMS)
Operating system(s): Windows
Software version: 5.1.1.7
Software edition:
Reference #: 1223158
IBM Group: Software Group
Modified date: Nov 18, 2005