| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ9456 when FRs & CHLs are all time running |
« View previous topic :: View next topic » |
| Author |
Message
|
| issac |
 Posted: Thu Dec 18, 2014 3:03 pm Post subject: AMQ9456 when FRs & CHLs are all time running |
 |
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
Hello, expert
PRs are at WMQ V7.0.1.3 for AIX
FRs (2 in total) are at WMQ V7.1.0.3 for AIX.
All qmgrs are located in the same data center.
All channels were never stopped. We have CHS monitored. AMQERR0X.LOG also verifies the conclusion.
The cluster is correctly defined. CLUSSDRs are pointing at FRs.
But this has just been found repeatedly reporting everyday.
| Code: |
----- amqrmrsa.c : 533 --------------------------------------------------------
12/17/14 21:50:09 - Process(1622252.1) User(mqm) Program(amqrrmfa)
Host(GWEGSP01)
AMQ9456: Update not received for queue LOCALQ.C.ABRCAST01.REQ, queue manager
MQEGSPBK2_2011-07-01_22.16.50 from full repository for cluster EGSPCLUSTER.
EXPLANATION:
The repository manager detected a cluster queue that had been used sometime 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 from when the error first occurred.
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.
|
The queue exists and should NOT be removed. The most funny part is : our FRs are running, chls are running, how could it not receive an update?
It is reporting for virtually ALMOST EVERY QUEUE. There are so many queues being reported that it for sure is going to be a disaster if they become unavailable.
The only thing I noticed a little special about this system is:
Hosts for both of FRs have 2 ips in the same subnet. All ports of these 2 ips are accessible to all other qmgr hosts.
Take FR1 for example, it has:
IP1
IP2
When we define CLUSSDRs, we picked IP2. However it seems that when the auto-defined CLUSSDRs are defined, CHS on a PR shows the connection is from IP1. Could QMGR internally take IP as part of the FR's ID to verify if an update is received?
We don’t know if this is related to the problem. When FR1 & FR2 were firstly made FRs on about 20140908, we checked logs 2 days and 1 month afterwards, this AMQ9456 was not spotted at the time. But these 2 hosts have always been configured with 2 ips each. Therefore to have 2 ips in the same subnet is at least not always causing a problem.
Thanks in advance.
_________________
Bazinga! |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Mon Dec 29, 2014 8:47 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Having two IPs is not a problem. Auto CLUSSDR are defined off the CLUSRCVR of the target machine. What is in the CONNAME of the CLUSRCVR? I bet it is IP1.
The two FRs have explicit CLUSSDR channels pointed at one another, correct? |
|
| Back to top |
|
|
| mvic |
| Posted: Tue Dec 30, 2014 2:16 pm Post subject: Re: AMQ9456 when FRs & CHLs are all time running |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| Did you run REFRESH CLUSTER on your Full Repository 30+ days ago? If so, maybe you have suffered IC81583 on this Partial as a result of that bug. Even if it wasn't that, check through all the APARs saying "cluster" in their descriptions since 7.0.1.3. Your systems are at risk of hitting known (fixed!) bugs including from "HIPER" APAR IV25030. |
|
| 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
|
|
|
|
