Author |
Message
|
techno |
Posted: Tue Aug 08, 2006 11:39 am Post subject: cluster channel inactive |
|
|
Chevalier
Joined: 22 Jan 2003 Posts: 429
|
We have four qmgrs in a cluster( 2 Full Rep, 2Parti Rep) . What we found today is one of the partial qmgr's clussdr went inactive(because of disconnect interval). And it did not have any cluster queues info. Then I started the clussdr and refreshed the cluster. I am sure something is wrong here. Full repo has to always communicate with partial repo, right!
Could you provide some hints when does this happen? |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Aug 08, 2006 12:00 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I don't think you had a problem. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
techno |
Posted: Tue Aug 08, 2006 12:06 pm Post subject: |
|
|
Chevalier
Joined: 22 Jan 2003 Posts: 429
|
So, is that normal? Doesn't partial repo get updated before loosing cluster info? |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Aug 08, 2006 12:20 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Partial repositories only store the information on the cluster objects they themselves host and cluster objects on other queue managers that have been requested recently.
If the cluster sender channel goes INACTIVE (which is a state that does not indicate an error), then it seems clear that nobody has requested anything recently. So if the qmgr doesn't host any qlocals that are shared in the cluster, then
In all cases, before doing ANYTHING with cluster channels, it is best to use amqsput to confirm that you can look up an object in the cluster! _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
techno |
Posted: Thu Aug 10, 2006 1:15 pm Post subject: |
|
|
Chevalier
Joined: 22 Jan 2003 Posts: 429
|
okay, let me present the scenario ...
FRQM-FullRepQmgr
PRQM-PartiRepQmgr
PRQM2------------>FRQM2 <------------------> FRQM1<------------PRQM1
When refreshed the cluster, PRQM2 established connection to PRQM1 and FRQM1 and otherway.
From Cluster manual:
Quote: |
When a queue manager sends out some information about itself, for example to
advertise the creation of a new queue, the full and partial repository queue
managers store the information for 30 days. To prevent this information from
expiring, queue managers automatically resend all information about themselves
after 27 days. If a partial repository sends a new request for information part way
through the 30 day lifetime it sees an expiry time of the remaining period. When
information expires, it is not immediately removed from the repository. Instead it is
held for a grace period of 60 days. If no update is received within the grace period,
the information is removed. The grace period allows for the fact that a queue
manager may have been temporarily out of service at the expiry date. If a queue
manager becomes disconnected from a cluster for more than 90 days, it stops being
part of the cluster. However, if it reconnects to the network it will become part of
the cluster again. Full repositories do not use information that has expired to
satisfy new requests from other queue managers. |
It says the qmgrs resend the info automatically before the expiry (after 27 days). I guess this did not happen in my case and I had to refersh manually.
Pls advise what to do for automatic update to happen. |
|
Back to top |
|
 |
Anirud |
Posted: Thu Aug 10, 2006 4:33 pm Post subject: |
|
|
 Master
Joined: 12 Feb 2004 Posts: 285 Location: Vermont
|
techno wrote: |
It says the qmgrs resend the info automatically before the expiry (after 27 days). I guess this did not happen in my case and I had to refersh manually.
|
It also says that the information will be deleted after 60 days (90 days in total).
I would assume that you did a qc(*) on the PRQM2 and found no cluster queues. That could be because the queue was not used for 90 days.
As Jeff suggested, try to do an amqsput and see if that works. If you get a 2085, then you have an issue.
Cheers. |
|
Back to top |
|
 |
Nigelg |
Posted: Fri Aug 11, 2006 6:09 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
Quote: |
Pls advise what to do for automatic update to happen. |
Nothing. The clue is in the word automatic
Also, how can it be so difficult to spell the word losing, meaning not being able to find something.
Why do so many people spell it loosing, which means to loosen, unfasten, to make less tight, etc. _________________ MQSeries.net helps those who help themselves.. |
|
Back to top |
|
 |
|