| Author |
Message
|
| Blomman |
 Posted: Tue Nov 13, 2012 6:47 am Post subject: |
 |
|
Master
Joined: 31 Oct 2006
Posts: 230
|
| mqjeff wrote: |
MO71 isn't going to use any different method than MQ Explorer or runmqsc to connect and talk to the remote queue manager.
Presumably you've already determined that you can't use a client connection to talk to QmB.
That leaves you with talking to QmB via an intermediate queue manager, regardless of what program you use to support it.
|
Yeah just figured tht one out while looking in the MO71 manual, it is just another "client" and will not solve the actual problem that is on another level.
| mqjeff wrote: |
As we said, the only way to make this work is to make sure that the reply messages can be routed back to QmA.
As we've said, in order for this to work, the remote xmitq must be *exactly* the same name as the value put in the replytoqmgr field of the request message.
The easiest way to find out what is in the replytoqmgr field is to stop the sender and look at the outgoing request messages on the xmitq on QmA. |
Yep will look into it when i back on site.
And this was my first approach from the beginning.
Just wanted too check here at the place with all the knowledge, if any special requirements was needed for this.
The docs dont say that any special is required and since my first simple test didnt work i asked the question.
//B |
|
| Back to top |
|
 |
| zpat |
| Posted: Tue Nov 13, 2012 7:18 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Blomman wrote: |
| mqjeff wrote: |
MO71 isn't going to use any different method than MQ Explorer or runmqsc to connect and talk to the remote queue manager.
|
Yeah just figured tht one out while looking in the MO71 manual, it is just another "client" and will not solve the actual problem that is on another level.
|
Wrong about MO71 - It connects to QM A as a client, it can then connect to QM B via the sender/receiver channel between A and B.
I am not known for making entirely pointless suggestions. So please assume that I am not an idiot.
I use this method for precisely the same reason. I have QM A allowed to talk to QM B through a firewall.
I use MO71 to administer QM B by connecting MO71 to QM A as a client, and then using the "via QM" option when defining the QM B location in MO71. |
|
| Back to top |
|
|
| Blomman |
| Posted: Tue Nov 13, 2012 7:46 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
[quote="zpat"]
| Blomman wrote: |
| mqjeff wrote: |
MO71 isn't going to use any different method than MQ Explorer or runmqsc to connect and talk to the remote queue manager.
|
Yeah just figured tht one out while looking in the MO71 manual, it is just another "client" and will not solve the actual problem that is on another level.
|
| zpat wrote: |
Wrong about MO71 - It connects to QM A as a client, it can then connect to QM B via the sender/receiver channel between A and B.
|
Ok is this different from MQExplorer?
| zpat wrote: |
I am not known for making entirely pointless suggestions. So please assume that I am not an idiot.
|
I didnt asume anything about you, i was just making my own assumtions from reading the MO71 manual
| zpat wrote: |
I use this method for precisely the same reason. I have QM A allowed to talk to QM B through a firewall.
I use MO71 to administer QM B by connecting MO71 to QM A as a client, and then using the "via QM" option when defining the QM B location in MO71. |
Yep will test this. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 13, 2012 8:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
[quote="Blomman"]
| zpat wrote: |
| Blomman wrote: |
| mqjeff wrote: |
MO71 isn't going to use any different method than MQ Explorer or runmqsc to connect and talk to the remote queue manager.
|
Yeah just figured tht one out while looking in the MO71 manual, it is just another "client" and will not solve the actual problem that is on another level.
|
| zpat wrote: |
Wrong about MO71 - It connects to QM A as a client, it can then connect to QM B via the sender/receiver channel between A and B.
|
Ok is this different from MQExplorer? |
No. It's not.
MQExplorer and MO71 have exactly the same methods of managing any given queue manager: using a bindings connection, using a client-connection, or using request-reply through any other qmgr.
Both MQExplorer and MO71 can use request-reply through a qmgr that is connected to using a bindings connection or through a client-connection.
Runmqsc can *not* establish a client connection. So it can only talk directly to a local qmgr, or it can control another qmgr using request-reply.
The suggestion to use MO71 does absolutely nothing to resolve the issue with reply messages not coming back from the remote qmgr. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Nov 13, 2012 11:51 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The problem might still be in the firewall. Are you sure that QMB is allowed to talk to QMA? It could well be that QMA is only allowed to talk to QMB but QMB cannot talk to QMA...
Even though the communication on MQ channels is now bi-directional, data and initiation still goes only one way (sender, receiver pairs)?
Do you have a requester channel on QMA and a server channel on QMB?
If so do you start the requester channel after having initiated the admin operation for QMB via QMA? What is the channel timeout set at?
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Blomman |
| Posted: Thu Nov 29, 2012 11:30 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
| fjb_saper wrote: |
The problem might still be in the firewall. Are you sure that QMB is allowed to talk to QMA? It could well be that QMA is only allowed to talk to QMB but QMB cannot talk to QMA...
Even though the communication on MQ channels is now bi-directional, data and initiation still goes only one way (sender, receiver pairs)?
Do you have a requester channel on QMA and a server channel on QMB?
If so do you start the requester channel after having initiated the admin operation for QMB via QMA? What is the channel timeout set at?
Have fun |
Might be an firewall issue, but we are running "normal" wmq traffic without any problems both ways(sender receiver channel pairs both ways).
However channels are triggered and a message seems to appeares on SYSTEM.ADMIN.COMMAND.QUEUE on QMA and gets consumed,but still i get timeout. Reservation on this one i could be another admin that are running commands on QMA.
I run this: runmqsc -m QMA -w 30 QMB.
This is QMA(Linux) <Firewall> QMB(Windows)
If i run the same runmqsc like this:
QMA(Linux) <No firewall> QMC(Linux)
It works.
Do the first setup require requester <-> server channels? Couldnt be any difference here.
So the only thing that differs is the firewall..
//Blomman
Last edited by Blomman on Thu Nov 29, 2012 11:34 am; edited 2 times in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 29, 2012 11:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
A message appears on SYSTEM.ADMIN.COMMAND.QUEUE? On which queue manager?
And it sits there? Or is processed?
Is there a message sitting on a transmission queue somewhere?
Is there a message sitting on a DLQ somewhere? |
|
| Back to top |
|
|
| Blomman |
| Posted: Thu Nov 29, 2012 11:36 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
| mqjeff wrote: |
A message appears on SYSTEM.ADMIN.COMMAND.QUEUE? On which queue manager?
And it sits there? Or is processed?
Is there a message sitting on a transmission queue somewhere?
Is there a message sitting on a DLQ somewhere? |
Updated my answer above.
Nothing on a transmission queue.
Nothing on a DLQ.
//Blomman |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 29, 2012 11:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
... I wouldn't expect to see a message on the command server queue on the qmgr you are connecting to - which I think is QMA.
It should only appear, briefly, on the transmision queue for QMA->QMB.
It should then appear on the command server queue on QMB.
QMB will then create a response message, which should go to the transmission queue QMB->QMA.
This will then appear on your dynamic replytoqueue on QMA, which is again not the command server queue.
Again, I would suggest that you stop the sender channel QMA->QMB, then use runmqsc.
This will cause a timeout.
But it should leave a message on the XMITQ for QMA->QMA.
You can examine this and see what the replytqmgr name is.
You can then ask the administrators of QMB to confirm that the name in the replytoqmgr is properly routable from their side, so that messages can come back to you.
You should also ask them if the command server on QMB is actually running.... And if you're allowed to access it.... |
|
| Back to top |
|
|
| Blomman |
| Posted: Thu Nov 29, 2012 11:59 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
| mqjeff wrote: |
... I wouldn't expect to see a message on the command server queue on the qmgr you are connecting to - which I think is QMA.
It should only appear, briefly, on the transmision queue for QMA->QMB.
It should then appear on the command server queue on QMB.
QMB will then create a response message, which should go to the transmission queue QMB->QMA.
This will then appear on your dynamic replytoqueue on QMA, which is again not the command server queue.
Again, I would suggest that you stop the sender channel QMA->QMB, then use runmqsc.
This will cause a timeout.
But it should leave a message on the XMITQ for QMA->QMA.
You can examine this and see what the replytqmgr name is.
You can then ask the administrators of QMB to confirm that the name in the replytoqmgr is properly routable from their side, so that messages can come back to you.
You should also ask them if the command server on QMB is actually running.... And if you're allowed to access it.... |
I will test this tomorrow!
Command server on QMB is running already verified this.
Ok i thougth the reply should appear on the command queue on QMA, your explain makes it at bit clearer.
//Blomman |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 29, 2012 12:06 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's possible that runmqsc uses the command server queue as it's reply to queue.
But I would not expect that. |
|
| Back to top |
|
|
| Blomman |
| Posted: Fri Mar 08, 2013 8:22 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
Havent got the time to take this up again until now..
However after further investigation the request messages (pcf, mqsc) is in DLQ ob qmB with "Auth" error code. User id is mqm from qmA but service account for wmq on qmB i have setup mqusr.
Local mqm group where service/ad account mqusr is member exists om win box. Did set mcauser to mqusr om rcvr channel on qmB but same problem appears.
Any suggestions? |
|
| Back to top |
|
|
|
|
