MQSeries.net :: View topic - Error in FR QMgr logs which is part of a cluster(on restart)

chris boehnke · Posted: Thu Jul 03, 2008 1:26 pm Post subject:

Hi Guys,
I am trying to make the QMgr, QM1 down and up after sometime(for maintenance). I am not touching any queues. When the QMgr, QM1 comes up its error log shows an error saying that the CLUSTER.QUEUE123 attributes are different on QM1 and QM2.(fyi: CLUSTER.QUEUE123 is a cluster queue and exists both on QM1 and QM2). I see the below errors on QM1 logs when the QMgr comesup. I compared attributes of the cluster queue CLUSTER.QUEUE123 on both the QMgrs QM1 and QM2 and the properties are one and the same except the 'OPPROCS'. Can you guys share your thoughts on this?.

The definition of cluster queue CLUSTER.QUEUE123 on the queue manager with UUID
QM1_2008-07-03_15.28.20 has different DEFPRTY, DEFPSIST and DEFBIND values
from the definition of the same cluster queue on the queue manager with UUID
QM2_2008-07-03_13.05.01. Both definitions now exist in the local
repository. All definitions of the same cluster queue should be identical. In
particular, problems arise if your applications rely on a queue default value
which is defined inconsistently to determine messaging behavior. This applies,
for example, if the applications open a cluster queue with option
MQOO_BIND_AS_Q_DEF. If different instances of the queue have different DEFBIND
values the behavior of the message transfer differs depending on which instance
of the queue is selected when it is opened. In general the instance selected
varies across opens.
ACTION:
For each inconsistency decide which of the values is the correct one. Alter the
definitions of cluster queue SSIF99609RSP so that all definitions have correct
DEFPRTY, DEFPSIST and DEFBIND values.

Thanks.