Team
we have MQ V 7.5 and we had 6 QMGR in cluster; and also we had 6 queues in cluster CLU1 and CLWLPRTY(9).
we have a requirement to expand the current foot print and add another 6 QMGRs and 6 queues to the same cluster CLU1. for some time in build phase we had CLWLPRTY(0) so that no messages flow to the newly added 6 cluster queues.
when we had to introduce new queues in production I made CLWLPRTY to '9' equal to existing cluster queues; but I do not see messages flowing to the new cluster queues. no readers / writers.
here is what I did to make sure our setup is good
- Verified all 12 cluster queues are visible from all 12 QMGRs.
- Just in case; I issues “REFRESH CLUSTER(CLU1)” on all full repository Qmanagers .
Issues “REFRESH CLUSTER(CLU1) REPOS(YES)” on all non-repository Qmanagers.
*** Not sure if I am missing anything to activate the new queues.
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
Studv01 wrote:
I have that covered too "DEFBIND" is set to "NOTFIXED" on all cluster queues.
It's also worth checking that the application doesn't explicitly set MQOO_BIND_ON_OPEN. _________________ Honesty is the best policy.
Insanity is the best defence.
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