| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ9456 |
« View previous topic :: View next topic » |
| Author |
Message
|
| meaton78 |
 Posted: Sat Dec 06, 2008 4:34 am Post subject: AMQ9456 |
 |
|
Centurion
Joined: 16 Oct 2008
Posts: 100
|
Does anyone have any experience with this error:
Update not received for queue <xxx>, queue manager <xxx> from full repository for cluster <xxx>.
I ran into an issue yesterday where an application was trying to put to a clustered queue and was getting the error that the queue was put disabled. We have 12 instances of that queue across 12 brokers, but only one is put enabled. When I did a dis QC(queue) on the application queue manager, I could only see one clustered queue. I had to refresh the cluster to get everything back. However, I'm not quite sure what scenarios would cause that to happen. Communication was fine between both full repositories and it had last connected to one of the FRs within the hour. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Sat Dec 06, 2008 9:38 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Just as best practice, make sure than none of the FRs are throwing errors, that the respository processes are running and that the cluster sender/receivers are working normally.
On which queue manager did you run the refresh? An FR or a PR?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| meaton78 |
| Posted: Sat Dec 06, 2008 10:50 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2008
Posts: 100
|
I did check the AMQERR logs and did not see anything obviously wrong on either FR. Also, amqrrmfa process was running on both boxes with no depth on either SYSTEM.CLUSTER.COMMAND.QUEUE.
The refresh was done on the PR since everyone else in that cluster was not experiencing any issues.
I know this may be difficult to diagnose, but I also know that first thing Monday I will be asked what went wrong. It's also a good learning experience for me. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Dec 06, 2008 3:19 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You're not at an older version of MQ, say prior to 5.3.0.12?
Next time it happens, try changing something on the PR queue that is not visible at the FR. Just change the q description by adding a period is enough.
At older MQ clusters (prior to 5.3.0.12) we would sometimes see this behaviour, and doing something to the q that altered it enough to have the PR tell the FR was enough. Obviously not a real solution. When we upgraded to CSD12 it went away, and we never have seen the problem at MQ 6.0.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| meaton78 |
| Posted: Sat Dec 06, 2008 8:19 pm Post subject: |
|
|
Centurion
Joined: 16 Oct 2008
Posts: 100
|
I will give that a shot although I'm hoping I will not see this again. We are on version 6, I believe either 6.0.2.0 or 6.0.2.1.
Do you think this could have anything to do with the subscriptions to the clustered queue? When the application started failing, I did not have time to troubleshoot, I had to get it running as fast as possible. I would have been interested to see what amqrfdm showed. |
|
| 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
|
|
|
|
