Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
The documentation is incorrect. There are pending requests to get the doc updated.
When you use MQ service Id to start a Broker, the primary group membership is mqm not mqbrkrs. This creates a permissions problem with a semaphore used by WebSphere Message Broker. A semaphore is created when the first broker starts after a reboot (or after an initial installation), and only members of the semaphore creator's primary group can access this semaphore. This problem is a consequence of the UNIX System V IPC primitives that are used by WebSphere Message Broker.
Any broker that is started by a user who'se primary group is not the semaphore creator's primary group ( ie. mqbrkrs ) causes the Broker to hang on subsequent mqsi commands.
That being said, HA failover may be acceptable to some. If you really want to dig into the issue, we should talk about the goals you have for high availability. Active-active provides more higher availability at less cost than active-passive in most goal-oriented analysis. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
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