| Author |
Message
|
| anthonyw |
 Posted: Wed Mar 07, 2007 2:02 am Post subject: MQ v5.3 QM stuck in suspend mode |
 |
|
Newbie
Joined: 07 Mar 2007
Posts: 3
Location: Edinburgh
|
Hi, I have came across a problem with an MQ cluster that has one of the repository QM stuck in suspend mode. I've tried to used the command to take it out of suspend mode but its not working. I'm new to the installation as the previous person left so I am trying to pick up the pieces of MQ, trying to get the two repository QMs talking again.
Its a problem because it is preventing other QMs from being added or removed from the cluster properly.
Anyone have any ideas or have came across this problem again?
We are using MQ v5.3 on 4 Windows servers, 2 of which are repositories and have 3 QMs each. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Mar 07, 2007 2:19 am Post subject: Re: MQ v5.3 QM stuck in suspend mode |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| anthonyw wrote: |
| We are using MQ v5.3 on 4 Windows servers, 2 of which are repositories and have 3 QMs each. |
Can I assume you mean there are 2 MQ repositories in the cluster, rather than 2 of the servers are repositories in an Windows clustering way?
First thing I'd check is the cluster channels linking the repositories, make sure they're running properly. Second thing is the log for that queue manager.
Third thing is promote one of the other queue managers to be a full repository (so you still have 2 in case of emergencies), then remove and re-add the suspended queue manager to the cluster. The third FR can then be demoted (or left - never hurts to have a spare spare!).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| anthonyw |
| Posted: Wed Mar 07, 2007 4:05 am Post subject: re:MQ v5.3 QM stuck in suspend mode |
|
|
Newbie
Joined: 07 Mar 2007
Posts: 3
Location: Edinburgh
|
Hi,
Yes it is just a MQ cluster and not a Windows cluster. I had checked the cluster channels when I was first looking at it and everything was communicating ok betweent he 2 repository QMs and the other QMs.
So next I had tried what you advised promoting one of the other QM as a full repository, this worked ok. I then removed the suspended QM from the cluster and tried to add it back in again. The result was that it added back in but it now shows as suspended? I tried this before I posted my question. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 07, 2007 4:28 am Post subject: Re: re:MQ v5.3 QM stuck in suspend mode |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| anthonyw wrote: |
| The result was that it added back in but it now shows as suspended? I tried this before I posted my question. |
At least we both had the same idea. Shame it didn't work..... 
So when you RESUME the queue manager there's no errors in the log? Does it record a resume attempt?
Also, how does this affect other queue managers being added or removed from the cluster? Obviously new queue manager would need to be pointed at one of the other FRs, but does the add or remove attempt fail? Are there any errors associated with that operation which could shed light?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| anthonyw |
| Posted: Wed Mar 07, 2007 7:14 am Post subject: re: Re: re:MQ v5.3 QM stuck in suspend mode |
|
|
Newbie
Joined: 07 Mar 2007
Posts: 3
Location: Edinburgh
|
Yes good to know I was thinking on the right lines.  Not so great it didn't work though. 
I'm going to check through the logs again to see if I can see anything, I know this has happened before and the last person had to create a new cluster instead.
When I try to ad a new QM to the cluster it is possible to get it to appear on one of the full repo cluster QMs but information doesn't get replicated to the other. I suspect that data in the repository QMs might be corrupt?
Cheers, Anthony. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 07, 2007 7:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Cluster repositories shouldn't get corrupted.
You can REFRESH CLUSTER if you want, or you can RESET it if you really believe it's corrupt.
You might also see if there are multiple instances of the queue manager (with different QMIDs) in the repository and then force remove the old ones.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Wed Mar 07, 2007 7:56 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
The most likely reason that a RESUME QMGR cmd is not working is that the repos mgr process (amqrrmfa) is not running on the qmgr. In that case, the msg to execute the command will sit on the cluster cmdq, and nothing will happen.
Check the process is running, and that there are no FDCs, and no msgs in the qmgr error log about the repos mgr process.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
|
|
