| Author |
Message
|
| PeterPotkay |
 Posted: Mon Sep 29, 2003 9:11 am Post subject: |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
In your error logs, it says that the channel started. Read that literally. The channel started, but the channel has several steps between starting and running (like initializing, binding, etc). So the message in the error log is simply telling you that you started the channel. That doesn't mean it made it all the way to running.
Refreshing, restarting, suspending, resuming, etc is not going to help here I don't think.
You say you changed the connection name parameter on the CLUSSNDR and the CLUSRCVR. On how many servers? Just this one? Did you change the CLUSSNDR on ServerA that points to ServerB, and forget to change the corresponding CLUSRCVR connection name parameter on ServerB?
Please post more details in your setup. How many servers involved, which connnames did you change on which server, etc.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| ajith_rajan |
| Posted: Mon Sep 29, 2003 9:15 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
I have only one machine in which I have two Q Managers that are part of the cluster. I have one cluster sender and cluster receiver channel in each qm. I have changed the IP address in the CONNAME parameter in both cluster sender and cluster receiver channels in both the QM.
As u said, it says that the channel has started but its trying to bind to the old IP address only. Its not taking the new one.
I have also tried suspend and resume as well.
Its not working.
Please let me know if there are anything else that needs to worked on.
Rgds
Ajith |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Sep 29, 2003 9:23 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
Stop all the CLUSSNDRS, then all the CLUSRCVRS.
Insure that all the connname parameters are OK.
Start the CLUSRCVRS channels only.
At this point on each QM, do:
| Code: |
display CLUSQMGR(Your QM Name) CHANNEL(your CLUSRCVR channel name) ALL
|
do this on both QMs and post the results. Are the conname parameters correct?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| ajith_rajan |
| Posted: Mon Sep 29, 2003 9:31 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
In the First QM,
display CLUSQMGR(LMUKGATEWAYQMNGR) CHANNEL(TO.LMUKGATEWAYQMNGR) ALL
1 : display CLUSQMGR(LMUKGATEWAYQMNGR) CHANNEL(TO.LMUKGATEWAYQMNGR) ALL
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(LMUKGATEWAYQMNGR) CLUSTER(GATEWAYCLUSTER)
CHANNEL(TO.LMUKGATEWAYQMNGR) CONNAME(10.146.34.142(1414))
QMID(LMUKGATEWAYQMNGR_2003-09-05_09.59.46)
DESCR( ) CLUSTIME(10.01.34)
CLUSDATE(2003-09-05) ALTTIME(11.51.47)
ALTDATE(2003-09-29) TRPTYPE(TCP)
DEFTYPE(CLUSRCVR) QMTYPE(REPOS)
MCANAME( ) MODENAME( )
TPNAME( ) BATCHSZ(50)
DISCINT(6000) SHORTRTY(10)
SHORTTMR(60) LONGRTY(999999999)
LONGTMR(1200) SCYEXIT( )
SCYDATA( ) SEQWRAP(999999999)
MAXMSGL(4194304) PUTAUT(DEF)
CONVERT(NO) MCAUSER( )
MCATYPE(THREAD) MREXIT( )
MRDATA( ) MRRTY(10)
MRTMR(1000) HBINT(300)
BATCHINT(0) NPMSPEED(FAST)
NETPRTY(0) SUSPEND(NO)
SSLCIPH( ) SSLCAUTH(REQUIRED)
BATCHHB(0) LOCLADDR( )
ALTTIME(11.51.47) ALTDATE(2003-09-29)
SSLPEER()
SENDEXIT( )
SENDDATA( )
MSGEXIT( )
MSGDATA( )
RCVEXIT( )
RCVDATA( )
In the Second QM, the output is
display CLUSQMGR(LMUKQMNGR1) CHANNEL(TO.LMUKQMNGR1) ALL
1 : display CLUSQMGR(LMUKQMNGR1) CHANNEL(TO.LMUKQMNGR1) ALL
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(LMUKQMNGR1) CLUSTER(GATEWAYCLUSTER)
CHANNEL(TO.LMUKQMNGR1) CONNAME(10.146.34.142(1415))
QMID(LMUKQMNGR1_2003-09-05_10.03.35) DESCR( )
CLUSTIME(10.05.11) CLUSDATE(2003-09-05)
ALTTIME(11.52.56) ALTDATE(2003-09-29)
TRPTYPE(TCP) DEFTYPE(CLUSRCVR)
QMTYPE(REPOS) MCANAME( )
MODENAME( ) TPNAME( )
BATCHSZ(50) DISCINT(6000)
SHORTRTY(10) SHORTTMR(60)
LONGRTY(999999999) LONGTMR(1200)
SCYEXIT( ) SCYDATA( )
SEQWRAP(999999999) MAXMSGL(4194304)
PUTAUT(DEF) CONVERT(NO)
MCAUSER( ) MCATYPE(THREAD)
MREXIT( ) MRDATA( )
MRRTY(10) MRTMR(1000)
HBINT(300) BATCHINT(0)
NPMSPEED(FAST) NETPRTY(0)
SUSPEND(NO) SSLCIPH( )
SSLCAUTH(REQUIRED) BATCHHB(0)
LOCLADDR( ) ALTTIME(11.52.56)
ALTDATE(2003-09-29) SSLPEER()
SENDEXIT( )
SENDDATA( )
MSGEXIT( )
MSGDATA( )
RCVEXIT( )
RCVDATA( )
I see the connection name here is correct.
Rgds
Ajith |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Sep 29, 2003 9:37 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
LMUKGATEWAYQMNGR lives on 10.146.34.142 and is listening on 1414.
LMUKQMNGR1 lives on 10.146.34.142 and is listening on 1415.
OK, now start the CLUSSNDRs and do the same DISPLAY for the CLUSSNDRs. Please post.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| ajith_rajan |
| Posted: Mon Sep 29, 2003 9:43 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
The Problem is I am not able to start the cluster sender channels.
And anyway, the following is the output I get on typing the given command.
display CLUSQMGR(LMUKGATEWAYQMNGR) CHANNEL(TO.LMUKQMNGR1) ALL
5 : display CLUSQMGR(LMUKGATEWAYQMNGR) CHANNEL(TO.LMUKQMNGR1) ALL
AMQ8147: WebSphere MQ object LMUKGATEWAYQMNGR not found.
Rgds
Ajith |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Sep 29, 2003 9:50 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
OK, the QM does not believe you have an object by this name. The error is a bit misleading, as it is says you don't have LMUKGATEWAYQMNGR, but it really means the CLUSSNDR channel is not known.
As a test, try issuing the command for the CLUSRCVR channel again, but this time misspell the channel name. It will tell you that LMUKGATEWAYQMNGR is not there, when we know it is and the channel is.
So, the real problem is that the QM does not believe TO.LMUKQMNGR1 exists. Yet you say you tried to start it. How? Thru the MQExplorer GUI? Ehh! issue the start command for TO.LMUKQMNGR1 from the command line and lets see what that says:
runmqsc LMUKGATEWAYQMNGR
START CHANNEL (TO.LMUKQMNGR1)
What happens here?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| ajith_rajan |
| Posted: Mon Sep 29, 2003 9:54 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
Check out whether TO.LMUKQMNGR1 exists or not???
AMQ8417: Display Channel Status details.
CHANNEL(TO.LMUKQMNGR1) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
CONNAME(137.46.225.85(1415)) CURRENT
CHLTYPE(CLUSSDR) STATUS(BINDING)
RQMNAME()
start channel(TO.LMUKQMNGR1)
3 : start channel(TO.LMUKQMNGR1)
AMQ9514: Channel 'TO.LMUKQMNGR1' is in use.
Rgds
Ajith |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Sep 29, 2003 9:56 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
Please issue this:
DISPLAY CHANNEL(TO.LMUKQMNGR1) ALL
Post the results.
I think I know what the problem is.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| ajith_rajan |
| Posted: Mon Sep 29, 2003 9:57 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
display channel(TO.LMUKQMNGR1) ALL
4 : display channel(TO.LMUKQMNGR1) ALL
AMQ8414: Display Channel details.
CHANNEL(TO.LMUKQMNGR1) CHLTYPE(CLUSSDR)
TRPTYPE(TCP) DESCR( )
MCANAME( ) MODENAME( )
TPNAME( ) BATCHSZ(50)
DISCINT(6000) SHORTRTY(10)
SHORTTMR(60) LONGRTY(999999999)
LONGTMR(1200) SCYEXIT( )
SEQWRAP(999999999) MAXMSGL(4194304)
CONVERT(NO) SCYDATA( )
USERID( ) PASSWORD( )
MCATYPE(THREAD) CONNAME(10.146.34.142(1415))
HBINT(300) BATCHINT(0)
NPMSPEED(FAST) SSLCIPH( )
BATCHHB(0) LOCLADDR( )
MCAUSER( ) CLUSTER(GATEWAYCLUSTER)
CLUSNL( ) ALTDATE(2003-09-29)
ALTTIME(11.51.2 SSLPEER()
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( ) |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Sep 29, 2003 10:20 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
Hmmm, well, it seems the cluster repository queue for some reason wont let go of the old IP address on the cluster senders.
If it were me, and this was my test system, and there are only 2 QMs involved, would do the following at this point:
Do this at your own risk. If you mess up, the QM can become unfuctional. This does work though, as we have done it a few times and even IBM has told us to do it once.
1.) STOP the CLUSSNDRs.
2.) STOP the CLUSRCVRs.
3.) Check all your definitions for queues, channels and the queue managers to make sure it is correct.
4.) PUT and GET INHIBIT the SYSTEM.CLUSTER.COMMAND.QUEUE. This cause the Cluster Repository Manager to crash, releasing its hold on the SYSTEM.CLUSTER.REPOSITORY.QUEUE.
5.) Clear the SYSTEM.CLUSTER.REPOSITORY.QUEUE. This blows away any old junk.
!!!!!!!!!!!!!!! VERY IMPORTANT STEP #6 If you skip this, you will forever destroy your queue manager.!!!!!!!!!!
6.) Reenable the SYSTEM.CLUSTER.COMMAND.QUEUE for both gets and puts. You must do this step.
7.) Restart the queue manger. This will also restart the repository manager as well.
8.)Start the CLUSRCVRs.
9.) Start the CLUSSNDRs.
Your SYSTEM.CLUSTER.REPOSITORY.QUEUEs are now built from scratch, with only correct info.
DON'T SKIP STEP NUMBER 6!!!!!
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| ajith_rajan |
| Posted: Mon Sep 29, 2003 10:24 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
I would try this out. Hope it works.
I do not know the commands to execute the steps 4,5 and 6.
Can u please let me know the commands I need to execute??
Thanks
Ajith |
|
| Back to top |
|
|
| ajith_rajan |
| Posted: Mon Sep 29, 2003 10:33 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
Let me know if these are the commands I need to execute
4) ALTER QLOCAL(SYSTEM.CLUSTER.COMMAND.QUEUE) PUT(DISABLED)
ALTER QLOCAL(SYSTEM.CLUSTER.COMMAND.QUEUE) GET(DISABLED)
5) CLEAR QLOCAL(SYSTEM.CLUSTER.COMMAND.QUEUE)
6) ALTER QLOCAL(SYSTEM.CLUSTER.COMMAND.QUEUE) PUT(ENABLED)
ALTER QLOCAL(SYSTEM.CLUSTER.COMMAND.QUEUE) GET(ENABLED)
Please confirm.
Rgds
Ajith |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Sep 29, 2003 10:35 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
That is pretty basic stuff, steps 4,5 and 6. No offense, but if you can't handle that, you really shouldn't be messing with Clustering under the covers.
Anyway, on each QM,
#4 ALTER QLOCAL(SYSTEM.CLUSTER.COMMAND.QUEUE) GET(DISABLED) PUT(DISABLED)
#5 ) CLEAR QLOCAL(SYSTEM.CLUSTER.COMMAND.QUEUE)
#6 ALTER QLOCAL(SYSTEM.CLUSTER.COMMAND.QUEUE) GET(ENABLED) PUT(ENABLED)
Do each step on each QM in order. What I mean is do step 1 on both QMs, then do step 2 on both QMs, etc.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| ajith_rajan |
| Posted: Mon Sep 29, 2003 10:53 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
This is not working.
Its still pointing to the same old IP address only.
I am not sure what the actual problem is.
I have done all the steps u had told me..
Rgds
Ajith |
|
| Back to top |
|
|
|
|
