| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| cluster channel problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| paul0al |
 Posted: Fri May 31, 2002 12:43 pm Post subject: cluster channel problem |
 |
|
Apprentice
Joined: 30 May 2002
Posts: 26
|
| I successfully created a cluster. However after setting up 2 queues and 2 queue managers, one of 2 cluster sender channels refuses to work. I have qm1 on machine 1 and qm2 on machine 2. The cluster send and receive channels for qm1 works fines and can communicate with qm2. The receive channels for qm2 works fine, but the send channels does not connect with qm1. I made sure all send and receive names match and communicating on the correct protocol. Any ideas? Thanks. |
|
| Back to top |
|
 |
| bduncan |
| Posted: Sun Jun 02, 2002 9:26 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Well, I don't quite understand your setup. You mentioned that both the cluster sender and receiver channels on qm1 are working fine, but only the receiver channel on qm2 is working. Channels always work in pairs. For every sender channel, there is a matching receiver channel somewhere. More importantly, each channel in a channel pair will always have the same channel status. To illustrate, let's say you channel names follow the convention qmX.to.qmY. If you have a sender channel on qm1 called qm1.to.qm2, and its status is RUNNING, then the corresponding receiver channel on qm2 (also called qm1.to.qm2) should also be running. But you say the sender channel on qm2 isn't working. But this means the matching receiver channel on qm1 should also not be working, but in your description you say it is.
To diagnose what is going on, I would say issue PING CHANNEL on the sender channel on qm2 that isn't working. Also try checking the logs for qm2.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Mon Jun 03, 2002 1:00 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hi guis...,
try the display channelstatus(*)
using runmqsc on both qmgrs. and let use see it here....
The reason why you don't see what you think or want might be because o f the sequence of creating the cluster channels, the sequence is mandatory, because MQSeries will create autodefined chgannes if you're doing it in the wrong sequence ... I had the trouble as well 
I hope this hint will help you...
My $0.02
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| paul0al |
| Posted: Tue Jun 04, 2002 8:37 am Post subject: better cluster problem explanation |
|
|
Apprentice
Joined: 30 May 2002
Posts: 26
|
| I created a cluster called "test_cluster." Within this cluster is 2 queue managers named QM_Ctata23 and QM_Calert28. Each queue manager contains one queue. In QM_Ctata23, the sender channel is called "TO_QM_Calert28" and the receiver channel is called "TO_QM_Ctata23." For QM_Calert28, the sender channel is called "TO_QM_Ctata23 " and the receiver channel is called "TO_QM_Calert28." The "TO_QM_Calert28" works fine, but the "TO_QM_Ctata23" is not working. On the QM_test_tata23 side, TO_QM_Ctata23 (sender) has a retrying status, while on the QM_Ctata23 side TO_AM_Ctata23 (receiver) is inactive. Any ideas on how to get the TO_QM_Ctata23 to get to a running status? I am running these queue managers and cluster on win2000 and I used the MQSeries explorer to set everything up. |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue Jun 04, 2002 9:46 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
I've had some problems in the past setting things up in MQExplorer, which is why I prefer to do everything from the runmqsc command line. I would recommend setting up the sample cluster as described in the MQ Clusters Manual using runmqsc. Do it in exactly the prescribed order - things can get really screwed up if you simply define things in the wrong order. As I said before, you should stop the sender channel that is retrying, and then issue a ping on it. Let us know what you get. Also check the logs.
Finally, you can try starting the channel manually so you can get a better idea of what is going on. Just stop the channel, and then from the command line, use the runmqchl command to start the sender channel directly. Presumably this command will fail and you will get a detailed error message as to why the channel can't start.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Wed Jun 05, 2002 11:50 pm Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hi Paul,
try issuing DIS CLUSQMGR(*) QMID under runmqsc on both qmgrs, and lets see what is in QMID...
It could say something like.. : QMID(SYSTEM.TEMPUUID.172.20.109.34(1414)
which means (as far as I see it) cluster defined in wrong sequence, it should look like : QMID(QSBT.B44C9A389E4B3D41)
By the way which version and CSD is it ??
I complete agree with Brandon in the way of setting the cluster up (as I mentioned before)..
An approch to circumvent the situation is to delete the failing qmgr and recreate it using commands. Not a pretty hint.. but it might help you.
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| 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
|
|
|
|
