Author |
Message
|
SOLOHERO |
Posted: Tue Jul 28, 2009 5:40 pm Post subject: TimeOut Function in multiple brokers |
|
|
Centurion
Joined: 01 Feb 2007 Posts: 107
|
Hi All,
Could you please help me with this query..
1. We are planning to have Cluster Broker(Clone of broker1)
2. we are using timoutnode and Timeout notification Nodes in the flows.
3. we send a request to a service timer starts in broker 1 and when we get the response back ..say if the response is comming to cluster broker then how will that cancel the timer as the timer was started in the broker1.
4. Cluster broker should know something about the start timer to cancel.
5. how can we solve this issue...i am pretty sure there will be many people using cluster brokers..
6. Please advise how to implement this and do we have to buy any fix packs for this.
Thanks in advance. _________________ Thanks |
|
Back to top |
|
 |
SOLOHERO |
Posted: Sun Aug 02, 2009 8:19 pm Post subject: |
|
|
Centurion
Joined: 01 Feb 2007 Posts: 107
|
could some one respond to this ..ASAP..Thanks _________________ Thanks |
|
Back to top |
|
 |
fschofer |
Posted: Mon Aug 03, 2009 12:23 am Post subject: |
|
|
 Knight
Joined: 02 Jul 2001 Posts: 524 Location: Mainz, Germany
|
Hi,
you could ensure that the response is send back to broker 1 by using sending queue manager name from the MQMD Header of the request message.
How this will be done depends on the setup of your MQ cluster
and the responding application.
Greetings
Frank |
|
Back to top |
|
 |
SOLOHERO |
Posted: Thu Aug 06, 2009 9:37 pm Post subject: |
|
|
Centurion
Joined: 01 Feb 2007 Posts: 107
|
we actually raised a pmr with IBM and they came up saying
You can only use TimeoutNotification and TimeoutControl Nodes within the
scope of a broker. The broker stores Timeout node information on the
SYSTEM.BROKER.TIMEOUT.QUEUE of the local broker qmgr. Since Broker qmgrs
cannot be shared, the scope of the Timout-type nodes is limited to the
broker.
You may be able to construct message flows that pass (user defined)
contol messages between msgflows running on different brokers using
WMQ queues to achive your aim.
So..we are thinking an option _________________ Thanks |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Aug 07, 2009 3:02 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
My understanding is that you have a request / response scenario.
Why would the responding app not send the response to the reply to qgmr?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
smdavies99 |
Posted: Fri Aug 07, 2009 3:29 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
fjb_saper wrote: |
My understanding is that you have a request / response scenario.
Why would the responding app not send the response to the reply to qgmr?  |
How about if they were not putting the real Qmgr Name but the Cluster QM Name as the Reply to Qmgr? _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
fschofer |
Posted: Fri Aug 07, 2009 3:41 am Post subject: |
|
|
 Knight
Joined: 02 Jul 2001 Posts: 524 Location: Mainz, Germany
|
smdavies99 wrote: |
How about if they were not putting the real Qmgr Name but the Cluster QM Name as the Reply to Qmgr? |
Hi,
so far i understand there are two brokers
"broker1" and "Clone of broker1" probably named broker2 which both have a underyling queue manager which are both in a cluster. Lets call them qm1 and qm2.
So which of these do you mean with real and Cluster ?
Greetings
Frank |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Aug 07, 2009 3:45 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
smdavies99 wrote: |
fjb_saper wrote: |
My understanding is that you have a request / response scenario.
Why would the responding app not send the response to the reply to qgmr?  |
How about if they were not putting the real Qmgr Name but the Cluster QM Name as the Reply to Qmgr? |
And the reason you'd shoot yourself in the foot is?
(Oh yeah, I went to that night club and was dancing when the gun went off!)
There are other ways to fix this if for security reasons the only default way back into the cluster is by cluster alias..., including sending a duplicate with expiry to the broker that did not get the message or publishing the message in the cluster (collective) to all brokers... (careful not to create an infinite loop, move correlid to usr folder and back after receiving the published msg ... )
 _________________ MQ & Broker admin |
|
Back to top |
|
 |
|