| Author |
Message
|
| pbravic |
 Posted: Fri Apr 02, 2004 8:28 am Post subject: amqrmfa - cluster issue |
 |
|
Apprentice
Joined: 24 Nov 2003
Posts: 42
|
|
| Back to top |
|
 |
| mqonnet |
| Posted: Fri Apr 02, 2004 8:43 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Think you misspelt it, you meant amqrrmfa.
That explains a lot of stuff. If the repository server process is not running, how can you expect subscription messages to be processed and updation of cache etc. Need to figure out the reason why it went down. Usually there should be some ffsts associated with this. Check them and post it here.
I thought you said you restarted your qm on unix. Repository server should start up fine on a qm restart unless there is a problem.
Also there ought to be more info in the mqerrlog that you posted in the other thread. Post that as well.
Cheers
Kumar |
|
| Back to top |
|
|
| pbravic |
| Posted: Fri Apr 02, 2004 12:58 pm Post subject: |
|
|
Apprentice
Joined: 24 Nov 2003
Posts: 42
|
Hi kumar
we had found the route cause of the issue, after restarting the unix qm the cluster_sender channel got into retrying state, upon investigation we find that channel connection was not correct (may be due to an another test activity carried last week).
we find when we see the channel connection parameter through MQexplorer properties its showing the correct one (host_ip(1414)
but while checking for the status by clicking on the channel the connectioname is pointing to wrong machine (dummyhost_ip(1414))
using dis chs(*) shows the particular channel in retrying state and connention name is also (dummyhost_ip(1414))
we want to change the connection name of the channel (host_ip(1414))
we had follwed most of the suggestions in the forum but the connection still remains the same.
pls let us know the way to change the connection parameter of the cluster_sender channel
thanks and regards
ravi |
|
| Back to top |
|
|
| pbravic |
| Posted: Fri Apr 02, 2004 9:09 pm Post subject: |
|
|
Apprentice
Joined: 24 Nov 2003
Posts: 42
|
hi
we couldn't find what is the cause why cluster sender channel is holding the incorrect connection info.
we tried removing the unix qm from the cluster and stopping all the cluster sender and reciever channels.
The dynamic channel and the sender channel still holds the dummy host connection parameter.
after removing the qm from cluster , we restarted the unix qm and did a refresh cluster(clname)
we did try issuing refresh cluster(clname) repos(yes) ==> this command doesn't work Is it allowed in MQseries 5.2? (as 5.2 is out of support we are not able to contact IBM support)
the dynamic cluster channel and cluster sender channel still holds the old connection name.
let us know to path to change the connection name and connect back to the cluster
regards
ravi |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Apr 02, 2004 10:09 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
Research the RESET command in the Cluster Manual. It will solve your problem.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| pbravic |
| Posted: Mon Apr 05, 2004 10:24 am Post subject: Solved - Clustering dynamic queue isssue |
|
|
Apprentice
Joined: 24 Nov 2003
Posts: 42
|
Hi Kumar and Peter
Thanks for your inputs. Since its a test system we took a risk by recreating the Unix QM and attaching it back to the cluster.
The steps followed
1) removing unix QM from cluster
2) Issuing reset command on the repository QMs
3) Recreate the unix QM
Even though the issue is solved. I want to know is there any way to remove the dynamic queue information from the unix QM (which is a partial repository QM)
once again thanks for your inputs
thanks and regards
ravi |
|
| Back to top |
|
|
|
|
