JMS Listener Port stops responding after a database failover or outage
 Technote (troubleshooting)
 
Problem(Abstract)
After a failover or database outage, the Java™ Message Service (JMS) listener ports stop.
 
Cause
A message driven bean (MDB) sends data to a database as part of the message processing. If the database is not available, as is the case during failover, the message delivery will fail. The message listener ports are designed to retry message delivery based on the "Maximum retries" parameter. If the delivery still fails after the "Maximum retries", then the listener port will stop.
 
Resolving the problem
You can resolve this issue by following the process below:

The default Maximum retries interval is 1 minute. Determine how long the database failover takes, and set Maximum retries to a value greater than the number of minutes the database will not be available. The message should be processed successfully and the listener port should not stop responding. The Maximum retries is the listener port recovery method. Once this number has been exceeded, the listener port requires a manual restart from the Administrative Console.

 
 
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
Software edition:
Reference #: 1176439
IBM Group: Software Group
Modified date: Aug 9, 2004