| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS/MDB Listener Doubt |
« View previous topic :: View next topic » |
| Author |
Message
|
| arunsridharan.india@gmail |
 Posted: Tue Jan 26, 2010 3:54 am Post subject: JMS/MDB Listener Doubt |
 |
|
Newbie
Joined: 08 Apr 2009
Posts: 4
|
Hi,
I have a doubt regarding JMS Listener in websphere which listens for messages from a local MQ queue.
There is a local MQ queue Q1.
There is a websphere JVM M1 which is part of the cluster C1 and I have configured JMS listener in M1 listening to Q1.
So wenever msg comes to Q1 the listener in JVM M1 triggers the mdb's onmessage in M1.
Everything fine…
Now if I add one more member M2 to my cluster C1 and create a JMS listener listening to the same Q1 what will happen. Where will the message be delivered. Will it be delivered to M1 or M2.
Will it be loadbalanced or some thing abnormal would happen…
Appreciate your views on this... |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jan 26, 2010 6:03 am Post subject: Re: JMS/MDB Listener Doubt |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| arunsridharan.india@gmail wrote: |
| Now if I add one more member M2 to my cluster C1 and create a JMS listener listening to the same Q1 what will happen. |
Nothing. Where your MDB is listening is a separate issue to the queue manager's membership (or not) of a cluster. All applications (even Java ones) connect to a queue manager not to the cluster. Hence an MDB on M2 can't connect to the instance of Q1 on M1, only the instance on M2.
There's nothing to stop you having multiple MDBs on M1 & M2, all servicing Q1 of course.
| arunsridharan.india@gmail wrote: |
Where will the message be delivered. Will it be delivered to M1 or M2.
Will it be loadbalanced or some thing abnormal would happen…
|
It will be delivered according to the configuration of the cluster & the wishes of the sending application. This remains true no matter how many MDBs are servicing the queues, or if no MDBs are servicing the queues, as MDB connection is a separate issue to clustering.
This question (or variations of it) has been asked many times in this forum for many reasons. A search & review of previous discussions may be informative for you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| J.D |
| Posted: Tue Jan 26, 2010 9:24 am Post subject: |
|
|
Voyager
Joined: 18 Dec 2009
Posts: 92
Location: United States
|
| I assume Cluster mentioned by Author is Application Server Cluster not the MQ Cluster. Multiple JMS listeners can be configured to a single Queue and there won't be any message duplication issues. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 26, 2010 9:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| J.D wrote: |
| I assume Cluster mentioned by Author is Application Server Cluster not the MQ Cluster. Multiple JMS listeners can be configured to a single Queue and there won't be any message duplication issues. |
Well given that this is posted in a WMQ forum I took a leap and assumed a WMQ cluster. Especially given the comment about loadbalancing, a function for which a WMQ cluster is often used.
If it is a WAS cluster then my comment about multiple MDBs still holds unless each WAS is sitting on top of it's own dedicated queue manager, in which case we're back in WMQ cluster territory.
In any event you won't get message duplication.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
