Effects of changing the Maximum messages property for JMS listener ports in WebSphere Application Server V5
 Technote (FAQ)
 
Problem
What can occur when the maximum messages property is changed from its default value of 1 on a JMS listener port in WebSphere® Application Server V5?
 
Solution
The Maximum messages property in the listener port configuration determines how many messages are removed from the queue and processed within a single transaction. If any of the messages cause the transaction to be rolled back, then all of the messages are returned to the queue to be reprocessed. This is undesirable behavior when there is only a problem with one message.

Another effect of increasing the Maximum messages property is that it will cause each transaction to run longer, which could cause transaction timeouts. The number of seconds that a transaction can run before timing out is configured in the Total transaction lifetime timeout setting in WebSphere Application Server. Its default value is 120 seconds.

For these reasons, it is recommended that the Maximum messages property not be changed from its default value of 1.

 
 
 


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 #: 1223180
IBM Group: Software Group
Modified date: Nov 18, 2005