MQSeries.net :: View topic

martin_thomas · Posted: Wed Mar 24, 2004 6:59 pm Post subject:

Using MQ v5.2, CSD 4

We have an MQ Clustered environment consisting of two overlapping clusters.

At the heart of this config are two full repositories, lets call them QM_FULL_REPOS_A and QM_FULL_REPOS_B, lets call the one of the cluster CL_APP and the other CL_USER.

Currently different parts of the cluster give a different view.

Eg QM's on the CL_APP side think that QM_FULL_REPOS_A is suspended and QM_FULL_REPOS_B is not.

QM's on CL_USER side think that QM_FULL_REPOS_B is suspend and QM_FULL_REPOS_A is not - these QM's can put messages onto the clustered queues on QM_FULL_REPOS_A but they do not get transferred to the CL_APP cluster. Instead they queue up on the SYSTEM.CLUSTER.TRANSMIT.QUEUE of QM_FULL_REPOS_A.

Internally QM_FULL_REPOS_A thinks nothing is suspended - using a "DIS CLUSQMGR(*) SUSPEND" shows no suspended QM's. However, despite this, try to add a new QM to cluster CL_APP and telling it to use QM_FULL_REPOS_A as the full repos manager gives a error saying QM_FULL_REPOS_A is currently suspended.

Doing the same on QM_FULL_REPOS_B shows both QM_FULL_REPOS_A and QM_FULL_REPOS_B as being suspended.

Although we can start and stop the queue managers, channels etc, we cannot get the 2 repositories to synchronise and this is causing a build-up of messages on the cluster transmission queues.

Can anyone please advise how we can force them to re-sync?