ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Clustering » CLuster queues attribu defined differntly in cluster members

Post new topic  Reply to topic
 CLuster queues attribu defined differntly in cluster members « View previous topic :: View next topic » 
Author Message
praveenmq
PostPosted: Sat Feb 25, 2012 4:38 am    Post subject: CLuster queues attribu defined differntly in cluster members Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 88

Hi All,

I am getting the below error on my cluster queues. This error is seen on both the members of clusters.

02/25/12 13:58:14 - Process(692272.1) User(mqm) Program(amqrrmfa)
Host(prdwas1)
AMQ9407: Cluster queue XXXXX is defined inconsistently.

EXPLANATION:
The definition of cluster queue XXXXX on the queue manager with UUID
EGP2XW14_2010-01-13_13.12.56 has different DEFPRTY, DEFPSIST and DEFBIND values
from the definition of the same cluster queue on the queue manager with UUID
EGP2XW13_2010-01-13_13.13.33. 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 XXXXX so that all definitions have
correct DEFPRTY, DEFPSIST and DEFBIND values.



The queue definition in both queue manager has only one value different in local queues. In one queue i have DEFPSIST(NO) and the other one i have as YES. Will change of this attribute will fix this error.

Also i browsed the messages in queue and it has messages from nov 27 2011 so is this not a major error?

Please advise what can be done..

Thanks in Advance.

Thanks,
Praveen.
Back to top
View user's profile Send private message
Vitor
PostPosted: Sat Feb 25, 2012 4:57 am    Post subject: Re: CLuster queues attribu defined differntly in cluster mem Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 21407
Location: Ohio, USA

praveenmq wrote:
The queue definition in both queue manager has only one value different in local queues. In one queue i have DEFPSIST(NO) and the other one i have as YES.


How did you manage that? There's clearly a problem with the scripting technology you use to build these objects, and the quality assurance process you use to verify them.

praveenmq wrote:
Will change of this attribute will fix this error.
. Read the error text.

praveenmq wrote:
Also i browsed the messages in queue and it has messages from nov 27 2011 so is this not a major error?


It's a major error is you have 2 identical applications relying on this value to set message persistence because in 1 case it's being set wrong.

I'd be far more worried about the 3 month old messages you have in these queues. Even if this isn't production these should have been cleaned up long ago. Again this points to a serious procedural problem.

praveenmq wrote:
Please advise what can be done..


Get a grip on your WMQ estate.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
praveenmq
PostPosted: Sat Feb 25, 2012 5:22 am    Post subject: Re: CLuster queues attribu defined differntly in cluster mem Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 88

How did you manage that? There's clearly a problem with the scripting technology you use to build these objects, and the quality assurance process you use to verify them.

----------Hi i just did display ql(name) and checked that these attributes are different in the qmgrs

Read the error text.

praveenmq wrote:
Also i browsed the messages in queue and it has messages from nov 27 2011 so is this not a major error?


It's a major error is you have 2 identical applications relying on this value to set message persistence because in 1 case it's being set wrong.

Hi This is a Production environment and these queues are not cleared so far. I am planning to clear the old messages first.

Also another update is like in the other cluster queue manger i can see the below error.

02/25/12 14:20:08 - Process(749662.10908) User(mqm) Program(amqzlaa0_nd)
Host(prdwas2)
AMQ7234: 10000 messages from queue 'XXXXX' loaded on queue manager
'EGP2XW14'.

EXPLANATION:
10000 messages from queue XXXXX have been loaded on queue manager
EGP2XW14.
ACTION:
None.
-------------------------------------------------------------------------------
02/25/12 14:20:08 - Process(749662.10908) User(mqm) Program(amqzlaa0_nd)
Host(prdwas2)
AMQ7234: 20000 messages from queue XXXXX loaded on queue manager
'EGP2XW14'.

EXPLANATION:
20000 messages from queue XXXXX have been loaded on queue manager
EGP2XW14.
ACTION:
None.
-------------------------------------------------------------------------------


It is loading the messages to the other member of the cluster queue manager. I dont know what exactly is happening here. Why it is loading the messages to the same queue in another queue manager.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Sat Feb 25, 2012 7:21 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 13423

You're confusing several different things.

Step back, take a deep breath.

Focus on exactly one thing at a time.

The thing you opened this post for was the fact that you have more than one instance of the same queue shared in a cluster.

At least one of those instances of the queue has a different set of parameters than the other instances in the cluster.

This is because the qlocal was defined differently. You need to alter the definition of the qlocal so that it is the same.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sat Feb 25, 2012 10:24 am    Post subject: Reply with quote

Jedi Council

Joined: 05 Jan 2008
Posts: 6789
Location: US: west coast, almost.

Moved to clustering forum.
_________________
I'm not paranoid; but the fellow following me is.
I have nothing to hide from the people I trust.

Energizer Bunny arrested! Charged with battery.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sat Feb 25, 2012 10:27 am    Post subject: Reply with quote

Jedi Council

Joined: 05 Jan 2008
Posts: 6789
Location: US: west coast, almost.

I strongly encourage you to search for messages and codes like AMQ7234 before you panic and post.

I went to google, entered AMQ7234 in the search box, and, voila!, found this: http://www-01.ibm.com/support/docview.wss?uid=swg21251301
_________________
I'm not paranoid; but the fellow following me is.
I have nothing to hide from the people I trust.

Energizer Bunny arrested! Charged with battery.
Back to top
View user's profile Send private message
Vitor
PostPosted: Sat Feb 25, 2012 1:09 pm    Post subject: Re: CLuster queues attribu defined differntly in cluster mem Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 21407
Location: Ohio, USA

praveenmq wrote:
Vitor wrote:
How did you manage that? There's clearly a problem with the scripting technology you use to build these objects, and the quality assurance process you use to verify them.


----------Hi i just did display ql(name) and checked that these attributes are different in the qmgrs


If you look carefully at what I typed (a process typically called reading) you'll observe I talked about how the queues were built. Not how you discovered the problem.



praveenmq wrote:
Hi This is a Production environment and these queues are not cleared so far. I am planning to clear the old messages first.


My point is why do you need to clear the messages? Why are they sitting unprocessed in production queues for 3 months?

praveenmq wrote:
Also another update is like in the other cluster queue manger i can see the below error.

02/25/12 14:20:08 - Process(749662.10908) User(mqm) Program(amqzlaa0_nd)
Host(prdwas2)
AMQ7234: 10000 messages from queue 'XXXXX' loaded on queue manager
'EGP2XW14'.

EXPLANATION:
10000 messages from queue XXXXX have been loaded on queue manager
EGP2XW14.
ACTION:
None.
-------------------------------------------------------------------------------
02/25/12 14:20:08 - Process(749662.10908) User(mqm) Program(amqzlaa0_nd)
Host(prdwas2)
AMQ7234: 20000 messages from queue XXXXX loaded on queue manager
'EGP2XW14'.

EXPLANATION:
20000 messages from queue XXXXX have been loaded on queue manager
EGP2XW14.
ACTION:
None.
-------------------------------------------------------------------------------


It is loading the messages to the other member of the cluster queue manager. I dont know what exactly is happening here. Why it is loading the messages to the same queue in another queue manager.


I echo the comments of my most worthy associates.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sat Feb 25, 2012 2:29 pm    Post subject: Reply with quote

Jedi Council

Joined: 05 Jan 2008
Posts: 6789
Location: US: west coast, almost.

I searched google for AMQ9407+infocenter. I quote from http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=%2Fcom.ibm.mq.amqzao.doc%2Frem.htm

Quote:
AMQ9407
Cluster queue <insert_3> is defined inconsistently.
Severity:

10 : Warning


A warning is not a fatal WMQ error.

The Explanation and Response in the InfoCenter (and the WMQ Messages manual) are clear as to the cause of the AMQ9407, the effect on your applications if the inconsistency remains, and the appropriate resolution.
_________________
I'm not paranoid; but the fellow following me is.
I have nothing to hide from the people I trust.

Energizer Bunny arrested! Charged with battery.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » CLuster queues attribu defined differntly in cluster members
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.