Setting the Maximum messages property for listener ports too high can cause transaction timeouts
 Technote (troubleshooting)
 
Problem(Abstract)
When using the WebSphere® Application Server V5 Message Listener Service, it is possible to configure a listener port so that more than one message per session can be processed by a Message-Driven Bean (MDB) associated with that listener port. If the Maximum messages property is set too high, transaction timeouts might occur.
 
Cause
The default value of the Maximum messages property is 1 for a listener port, meaning that only a single message is processed by an MDB in one session.
 
Resolving the problem
The Maximum messages property can be tuned by using the Administrative Console. In the Administrative Console, select the Application Server > Message Listener Service > Listener Ports, then select a defined listener port. This brings up the listener port properties, and Maximum messages can be adjusted here.

The Transaction Timeout Value can also be set in the Administrative Console. To adjust its value, select the Application Server, then choose Transaction Service. The default Total transaction lifetime timeout is 120 seconds and can be tuned upward if there are long-running transactions on the Application Server.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Business Integration WebSphere MQ
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.0
Software edition:
Reference #: 1165862
IBM Group: Software Group
Modified date: Sep 10, 2004