| Author |
Message
|
| jeevan |
 Posted: Fri Apr 04, 2008 1:15 pm Post subject: Urgetn help |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
I am getting an error 2087 at the relying queue manager. The steup is like this:
Application A connects to QMGR QMA and puts a message in a cluster Queue, lets say Q1. This messages ends up at Q1(local to qmgr QMB). It is working up to this point. There are listeters listening to the Q1 at QMB. Another app lets say B connected to QMGR QMB and picks up the message from QMB, processes it and sends a reply to a queue Q2 which is local queue at QMA. We are gettting error 2087 queue manager unknown in app log of app B. This sounds when it tries to write to response to queue Q2, it could not.
I checked the message headers at QMB before they are picked up ( stopped listener) boht of them replytoqmgr and replytoqueue look fine . what else can I check?
any suggestions |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Apr 04, 2008 2:37 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Cluster communications seem to not be working right.
Check for cluster sender/ receiver without the right cluster identification or that are not in a running mode...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Apr 04, 2008 3:06 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
Cluster communications seem to not be working right.
Check for cluster sender/ receiver without the right cluster identification or that are not in a running mode...
|
If that's ok, go through the rest of the cluster config. Check for mis-spelt cluster names (as common as mis-spelt queue names!)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Apr 07, 2008 8:21 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| Vitor wrote: |
| fjb_saper wrote: |
Cluster communications seem to not be working right.
Check for cluster sender/ receiver without the right cluster identification or that are not in a running mode...
|
If that's ok, go through the rest of the cluster config. Check for mis-spelt cluster names (as common as mis-spelt queue names!) |
It was working and nothing has been changed recently. We have not changed anything. I checked the replyto qmgr and queue on message header before they were picked up, and both seem correct. I can suspect the app, but it was working and the developer says nothing has been changed.
not sure what to check. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Apr 07, 2008 2:36 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Can you guarantee that there was no network hickup and such. If the PR cannot receive the FR's answer on the request for instances of the queue and the queue is not hosted by the PR the put will receive a 2087...
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jeevan |
| Posted: Tue Apr 08, 2008 7:32 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| fjb_saper wrote: |
Can you guarantee that there was no network hickup and such. If the PR cannot receive the FR's answer on the request for instances of the queue and the queue is not hosted by the PR the put will receive a 2087...
Enjoy |
Sorry. It was problem in cluster. The qmgrs in a partiuclar server were rebuilt a few days ago. There was wroing REPOSITORY name in the server channel of the queue manager where the message are picked by appl. So message were received, but not sent or remote queue manager unkonw (2087) error.
thanks for you input. I appreciate |
|
| Back to top |
|
|
|
|
