More than one MDB listeners Listening against the same Queue
 Technote (troubleshooting)
 
Problem(Abstract)
What are the pros and cons to consider when you configure more than one MDB listeners listening against the same message queue?
 
Resolving the problem
Having more than one MDB listener listening against the same queue without selection will cause poor performance. This is because the MDB listeners will compete for messages, but the benefit of high availability usually outweights that.
Currently with WebSphere Application Server 5.0.0 and WebSphere Application Server 5.0.1, if an application server that has an MDB on it listening to a queue dies, the MQ will still deliver messages to that queue regardless.

If the high availability of the MDBs is very important, then it is suggested to configure two separate application servers with an MDB on each, listening to the same MQ Queue. Therefore, if one goes down the other will still be consuming messages. These two MDBs (if active) will simply keep pulling messages from the queue. There is no real control over them other than manual control of the ListenerPort (stop/starting them).
 
 
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.0.1
Software edition:
Reference #: 1113301
IBM Group: Software Group
Modified date: Jun 23, 2003