| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Cluster error |
« View previous topic :: View next topic » |
| Author |
Message
|
| SimplyAniket |
 Posted: Thu Oct 02, 2008 11:13 pm Post subject: Cluster error |
 |
|
Novice
Joined: 13 Sep 2008
Posts: 13
|
I am receiving below error in my queue manager log
Process(10475.1) User(mqm) Program(amqrrmfa)
AMQ9456: Update not received for queue (queue name) queue manager
(queue manager name)_2008-01-02_13.40.55 from full repository for cluster (cluster name).
EXPLANATION:
The repository manager detected a queue that has been used in the last 30 days
for which updated information should have been sent from a full repository.
However, this has not occurred.
The repository manager will keep the information about this queue for a further
60 days.
ACTION:
If the queue is still required, check that:
1) The cluster channels to and from the full repository and the queue manager
that hosts the queue, are able to run.
2) The repository managers running on these queue managers have not ended
abnormally.
My repository queue manager was failed over due to unknown reason. What should i do for above error.
I checked the cluster receiver channel for the repository queue manager. It is up and running fine. MQ version is 6.0.2.3 |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Oct 03, 2008 2:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You need to check both ends of the channel.
If the FR failed over (I assume HA configuration) there should be very little difference. Make sure the Cluster Receiver on the HA governed cluster uses the virtual IP of the HA cluster and not the ip of the physical host.
And read up in the cluster manual when there is an adequate time / reason to call refresh cluster.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jhidalgo |
| Posted: Mon Oct 06, 2008 9:52 am Post subject: |
|
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
SimplyAniket:
this happens when you have one PR(partial repository) pointing to the wrong FR(full repositories), so the PR doesn't get updates on its cluster information OR you have the FR unavailable for more than 30 days.
so the solutions are:
If it is pointing to the right FR (make sure it is a FR and make sure you don't have more than 2 FRs), make sure your FR is available
If you have more than 2 FRs choose only 2 !,
Temporarly you can issue the refresh cluster information to the PRs and FRs so it get the updates but that will not fix your problem... only for 30 days... |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Oct 06, 2008 2:05 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
...or wait 91 days for the object definition to be flushed from the cluster.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| 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
|
|
|
|
