|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Triggering & Clusters |
« View previous topic :: View next topic » |
Author |
Message
|
kevinf2349 |
Posted: Tue Aug 03, 2004 12:05 pm Post subject: Triggering & Clusters |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
We have an application that (currently) gets triggered when a message arrives (type=first). That application reads any and all messages until the queue is empty and then terminates. Nothing too difficult here, just a straightforward triggered application (on Windows).
We are thinking of making the application use clusters. So my question is...how does triggering work on clustered queues? Does it only work on the owning queue manager? Would it be better to have all queue managers to actually have an instance of the clustered queue defined locally for triggering? Would it be better if the application were to be redesigned to start at IPL time and run until it is stopped manually?
Any input would be appreciated.
Thanks |
|
Back to top |
|
 |
EddieA |
Posted: Tue Aug 03, 2004 12:40 pm Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
Quote: |
how does triggering work on clustered queues |
Exactly the same way as on non-clustered. You can only GET from a local queue, so yes, you would need an instance of the triggered application on each QM that hosts the queue.
Quote: |
Would it be better if the application were to be redesigned to start at IPL time and run until it is stopped manually |
It depends.
How often are messages arriving. Do you want the message processed as fast as possible, or is the application start-up time not an issue.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
kevinf2349 |
Posted: Tue Aug 03, 2004 1:19 pm Post subject: |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
Thanks Eddie. The reply was pretty much what I was expecting. The application startup isn't an issue....yet....but given the nature of the application it may very well turn out to be. I admit I have a few misgivings about the whole design that the programmers have come up with...we shall see. At the moment I am really just looking ahead to what I suspect will be down the line and formulating some options.
Thanks again for the input. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Tue Aug 03, 2004 2:28 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
EddieA wrote: |
Quote: |
how does triggering work on clustered queues |
Exactly the same way as on non-clustered. You can only GET from a local queue, so yes, you would need an instance of the triggered application on each QM that hosts the queue.
|
Well, technicaly the app could be on another server connecting in Client mode to the QM that hosts the clustered queue. You would then need to employ the client trigger monitor as well. We have this happening in one of our clusters.
But that only strengthens Eddie's pont. There is absolutly no difference as far as triggering is concerned whether the triggered queue is clustered or not. _________________ Peter Potkay
Keep Calm and MQ On |
|
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
|
|
|
|