| Author |
Message
|
| ashritha |
 Posted: Mon Dec 12, 2005 7:29 am Post subject: Cluster Channel not starting |
 |
|
Voyager
Joined: 25 Jul 2005
Posts: 85
|
Hello,
I am trying to cluster 2 queue managers following an IBM document.
When I try to create cluster-sender channel on QM1 and cluster-receiver channel on QM2, they start very fine. But when I try to create cluster-sender on QM2 and Cluster-receiver on QM1, the sender channel always is in a retying stage and never starts.
When I tried creating simple sender on QM2 and receiver channels on QM1(not clulster sender and receiver), they work fine which tells me that there is no connectivity issue between the systems.
Can any one explain why am I unable to start the cluster sender channel from 1 queue manager while I am able to do it the other way?
Thanks in advance. |
|
| Back to top |
|
 |
| wschutz |
| Posted: Mon Dec 12, 2005 7:33 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
There might be a hint in the MQ error log (amqerr01.log)
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Dec 12, 2005 7:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You don't need to explicitly start the cluster senders.
It's probably better to try shutting both qms down, and starting them up again.
Then see what channels are running and which aren't.
Also, make sure you have set the right repository name on the qmgr.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ashritha |
| Posted: Mon Dec 12, 2005 10:30 am Post subject: |
|
|
Voyager
Joined: 25 Jul 2005
Posts: 85
|
The error that i can see in the Event Viewer is as follows:
| Quote: |
Remote host 'LPPCONSULT7 (10.11.141.120) (1414)' not available, retry later.
The attempt to allocate a conversation using TCP/IP to host 'LPPCONSULT7 (10.11.141.120) (1414)' was not successful. However the error may be a transitory one and it may be possible to successfully allocate a TCP/IP conversation later. |
The important points that need to be noted here is that the sender channel on the system LPPCONSULT7 is not running(in retrying stage) but the error considers LPPCONSULT7 as a remote host and is trying to listen to port 1414 when that port does not exist at all. I have my queuemanager running on 3333 and the other queuemanager that on the remote machine which needs to be a part of the cluster is listening to port 5555. the port 1414 does not exist on any of the machines.
I did not manually start the channels. The cluster-sender channel of one queue manager started automatically while the cluster-sender channel of the other queue manager remained in the retrying stage.
I also tried shutting down and restartingt he queue managers but found no difference.
Any other ideas???
I am following the same document that is specified in the documentations tab of this website. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Dec 12, 2005 10:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So you need to set the conname on the cluster sender channels to include the port number as well as the host name, in the same way that you set them when creating the regular channels...?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ashritha |
| Posted: Mon Dec 12, 2005 10:51 am Post subject: |
|
|
Voyager
Joined: 25 Jul 2005
Posts: 85
|
I did the same. The conname that i set has the ipaddress as well as the corresponding port number of the listerner the queue manager is running on.
Please note that one set of the cluster-sender, cluster-receiver channels work fine. but the other set from Sending from QM2 does not work.
I am setting the values exactly the same for both senders and receivers.
Its really strange that one way of communication doesn't have any problem while the other way cannot connect.
If i create a simple sender and receiver channels both queuemanagers are able to send and receive from one another. The problem is only with one cluster-sender channel. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Dec 12, 2005 10:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Can you post the definition of both sides of the non-working channel?
Heck, can you post all four channels?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ashritha |
| Posted: Mon Dec 12, 2005 11:02 am Post subject: |
|
|
Voyager
Joined: 25 Jul 2005
Posts: 85
|
CHANNEL DEFINITIONS OF SYSTEM NJSP01A:
DEFINE CHANNEL(NJSP01A.NJSP01B) CHLTYPE(CLUSSDR) TRPTYPE(TCP) CONNAME('10.11.50.113 (5555)') CLUSTER(CLUSTER_PROD)
DEFINE CHANNEL(NJSP01B.NJSP01A) CHLTYPE(CLUSRCVR) TRPTYPE(TCP) CONNAME(10.11.50.113) CLUSTER(CLUSTER_PROD)
CHANNEL DEFINITIONS OF SYSTEM NJSP01B:
DEFINE CHANNEL(NJSP01B.NJSP01A) CHLTYPE(CLUSSDR) TRPTYPE(TCP) CONNAME('10.11.141.120 (3333)') CLUSTER(CLUSTER_PROD)
DEFINE CHANNEL(NJSP01A.NJSP01B) CHLTYPE(CLUSRCVR) TRPTYPE(TCP) CONNAME(10.11.141.120) CLUSTER(CLUSTER_PROD) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Dec 12, 2005 11:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I suppose I misspoke earlier.
The conname that is used is that on the clusrcvr, not the clussdr.
So add the port # to the clusrcvr and try again.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ashritha |
| Posted: Mon Dec 12, 2005 11:19 am Post subject: |
|
|
Voyager
Joined: 25 Jul 2005
Posts: 85
|
I tried adding the port number in the conname of the cluster receiver channels of both the queue managers. But have the same problem again.
Cluster-Sender channel on NJSP01B starts without any problem while the one on NJSP01A is in the retrying stage.
I tried shutting down and restarting the queue managers also, but did not help. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Dec 12, 2005 12:06 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| ashritha wrote: |
| I am setting the values exactly the same for both senders and receivers. |
Your channel defs are all wrong.
On Server1/QM1, the CLUSSNDR should have the conname/port # of Server2/QM2.
On Server1/QM1, the CLUSRCVR should have the conname/port # of Server1/QM1.
On Server2/QM2, the CLUSSNDR should have the conname/port # of Server1/QM1.
On Server2/QM2, the CLUSRCVR should have the conname/port # of Server2/QM2.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| EddieA |
| Posted: Mon Dec 12, 2005 12:09 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| ashritha wrote: |
CHANNEL DEFINITIONS OF SYSTEM NJSP01A:
DEFINE CHANNEL(NJSP01A.NJSP01B) CHLTYPE(CLUSSDR) TRPTYPE(TCP) CONNAME('10.11.50.113 (5555)') CLUSTER(CLUSTER_PROD)
DEFINE CHANNEL(NJSP01B.NJSP01A) CHLTYPE(CLUSRCVR) TRPTYPE(TCP) CONNAME(10.11.50.113) CLUSTER(CLUSTER_PROD)
CHANNEL DEFINITIONS OF SYSTEM NJSP01B:
DEFINE CHANNEL(NJSP01B.NJSP01A) CHLTYPE(CLUSSDR) TRPTYPE(TCP) CONNAME('10.11.141.120 (3333)') CLUSTER(CLUSTER_PROD)
DEFINE CHANNEL(NJSP01A.NJSP01B) CHLTYPE(CLUSRCVR) TRPTYPE(TCP) CONNAME(10.11.141.120) CLUSTER(CLUSTER_PROD) |
You're mixing up the CONNAMEs. The CLUSSDRs point to the Destination QM. The CLUSRCVs point to "this" QM. And you still need the ports on the CLUSRCVRs, because that't the definition that will be used by remote QMs to talk to "this" one.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| ashritha |
| Posted: Mon Dec 12, 2005 12:20 pm Post subject: |
|
|
Voyager
Joined: 25 Jul 2005
Posts: 85
|
Sorry Peter!
That doesn't work either. The sender channel is in the initializing stage. Never came out of it... as inactive or as retrying.....
but the second sender channel works fine as usually.
This was how both of them behaved with my older definitions too. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Dec 12, 2005 12:24 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Take the conname defs from that sender that is failing, log onto the sending server, and do a telnet to that other ip and port.
If the telnet fails, you got a network issue, or the listener is not up on the 2nd machine.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| ashritha |
| Posted: Mon Dec 12, 2005 12:30 pm Post subject: |
|
|
Voyager
Joined: 25 Jul 2005
Posts: 85
|
My new channel definitions are now as follows:
Note: IP address of sys A is 10.11.141.120 and sys B is 10.11.50.113
CHANNEL DEFINITIONS OF SYSTEM NJSP01A:
DEFINE CHANNEL(NJSP01A.NJSP01B) CHLTYPE(CLUSSDR) TRPTYPE(TCP) CONNAME('10.11.50.113 (5555)') CLUSTER(CLUSTER_PROD)
DEFINE CHANNEL(NJSP01B.NJSP01A) CHLTYPE(CLUSRCVR) TRPTYPE(TCP) CONNAME('10.11.141.120 (3333)') CLUSTER(CLUSTER_PROD))
CHANNEL DEFINITIONS OF SYSTEM NJSP01B:
DEFINE CHANNEL(NJSP01B.NJSP01A) CHLTYPE(CLUSSDR) TRPTYPE(TCP) CONNAME('10.11.141.120 (3333)') CLUSTER(CLUSTER_PROD)
DEFINE CHANNEL(NJSP01A.NJSP01B) CHLTYPE(CLUSRCVR) TRPTYPE(TCP) CONNAME('10.11.50.113 (5555)') CLUSTER(CLUSTER_PROD)
I still run on the same problem. The only difference is that now the sender channel that was creating problem from the beginning is in initializing stage while previously that was in retrying stage.
The other sender channel works fine as it did with my previous piece of code. |
|
| Back to top |
|
|
|
|
