| Author |
Message
|
| Ganapa |
 Posted: Tue Jun 26, 2012 7:37 am Post subject: Issue with multi-instance broker on WMB 8.0.0.0 |
 |
|
Newbie
Joined: 15 Apr 2012
Posts: 7
|
Hi,
We are using WMB 8.0.0.0 in one of our customer place and we are facing an issue while setting up multi-instance broker on SUSE Linux environmet.
Here are the details,
After setting up the broker on the active (host1) and passive (host2) VMs, I'm not able to create any execution group on the active broker and I'm getting the following error,
[quote]
BIP1124I: Creating execution group 'EG1' on broker 'TEST_BRK'...
BIP1047E: The operation timed out waiting for a response.
The utility did not receive an expected response from the broker within a designated amount of time. The operation might have completed successfully, even though the response was not received.
Ensure that the broker is running and that the correct connection parameters have been supplied to the utility. Use the -w flag to increase the amount of time to wait for responses.
[/quote]
Please note that both active and passive instances have already been started on host1 and host2.
Please let me know if anyone has come across this issue.
Thanks, |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Jun 26, 2012 7:54 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 26, 2012 7:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Or at least look at the log on the broker runtime server to see what it says is going on. |
|
| Back to top |
|
|
| ganesh |
| Posted: Tue Jun 26, 2012 7:59 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| We have already raised a PMR for this issue and it has been pending for more than 10 days. In the meantime we wanted to check if anyone else had encountered similar issue. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jun 26, 2012 7:59 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
What is the Service Id that is being used to run Broker? The Primary Group Id of the Service Id needs to be mqbrkrs not mqm.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 26, 2012 8:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| ganesh wrote: |
| We have already raised a PMR for this issue and it has been pending for more than 10 days. In the meantime we wanted to check if anyone else had encountered similar issue. |
You haven't given any useful information for anyone to tell.
Presumably there's a reason the PMR is taking so long, too.
Again, what does the system log on the machine running Broker say? |
|
| Back to top |
|
|
| ganesh |
| Posted: Tue Jun 26, 2012 8:07 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| Quote: |
| What is the Service Id that is being used to run Broker? The Primary Group Id of the Service Id needs to be mqbrkrs not mqm. |
We are using mqm as a service id to run the broker and the mqm id is part of mqbrkrs and mqm goup. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jun 26, 2012 8:09 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| ganesh wrote: |
| Quote: |
| What is the Service Id that is being used to run Broker? The Primary Group Id of the Service Id needs to be mqbrkrs not mqm. |
We are using mqm as a service id to run the broker and the mqm id is part of mqbrkrs and mqm goup. |
Thats why you have a problem. Never, ever use mqm as the service Id to start Broker.
| Quote: |
A semaphore is created when the first broker starts after a reboot (or after an initial installation), and only members of the primary group of the semaphore creator can access this semaphore. This problem is a consequence of the UNIX System V IPC primitives that are used by WebSphere Message Broker.
The BIP2228 message is logged by any broker that is started by a user who is not a member of the primary group of the semaphore creator. The broker tries to access the semaphore, but fails with a permissions-related error. The broker then terminates with the BIP2228 message.
Solution: Avoid this problem by ensuring that all user IDs used to start WebSphere Message Broker have the same primary group. If this action is impractical, ensure that all user IDs are members of primary groups of all other user IDs. Contact your IBM® Support Center for further assistance.
|
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jun 26, 2012 8:18 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| ganesh wrote: |
| Quote: |
| What is the Service Id that is being used to run Broker? The Primary Group Id of the Service Id needs to be mqbrkrs not mqm. |
We are using mqm as a service id to run the broker and the mqm id is part of mqbrkrs and mqm goup. |
mqm's Primary Group Id is mqm. Any user who starts Broker needs primary group membership of mqbrkrs. They need secondary group membership of mqm. Not the other way around. You're timing out because the semaphore is never able to be owned since the primary groups are different.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| ganesh |
| Posted: Tue Jun 26, 2012 8:22 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| mqjeff wrote: |
| ganesh wrote: |
| We have already raised a PMR for this issue and it has been pending for more than 10 days. In the meantime we wanted to check if anyone else had encountered similar issue. |
You haven't given any useful information for anyone to tell.
Presumably there's a reason the PMR is taking so long, too.
Again, what does the system log on the machine running Broker say? |
Jeff - We have sent IBM the trace and sys logs. Below is the trace details....
Sys log...
| Code: |
Jun 12 13:51:33 mb-test1 WebSphere Broker v8000[10193]:
(TEST_BRK)[1]BIP2111E: Message broker internal error: diagnostic
information 'ImbConfigStore::obtainHALock () reported 'Server name does not
match in ImbConfigStore::obtainHALock' with values... ''TEST_BRK'''. :
TEST_BRK.agent: /build/S000_P/src/AdminAgent/ImbAdminStore.cpp: 1300:
ImbAdminStore::tableInitialisation: :
Jun 12 13:51:33 mb-test1 WebSphere Broker v8000[10193]:
(TEST_BRK)[1]BIP2805E: Broker TEST_BRK could not process an internal
configuration message. :
TEST_BRK.agent: /build/S000_P/src/AdminAgent/ImbAdminAgent.cpp: 2494:
ImbAdminAgent::analyseInputMessageCommands: :
Jun 12 13:51:33 mb-test1 WebSphere Broker v8000[10193]:
(TEST_BRK)[1]BIP8238E: The multi-instance broker TEST_BRK has detected that
another broker instance is active. This broker instance stops and restarts
to maintain integrity of the broker data. :
TEST_BRK.agent: /build/S000_P/src/DataFlowEngine/ImbConfigStore.cpp: 2079:
ImbConfigStore::obtainHALock : :
Jun 12 13:51:33 mb-test1 WebSphere Broker v8000[10193]:
(TEST_BRK)[15]BIP2111E: Message broker internal error: diagnostic
information 'ImbConfigStore::throwConfigStoreHALockException() reported
'CSHA005' with values... ''TEST_BRK'''. :
TEST_BRK.agent: /build/S000_P/src/AdminAgent/ImbDeployManagerCacheBroker.cpp:
|
|
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jun 26, 2012 8:24 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 26, 2012 8:25 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Oh look! Real Data! That indicates that the Broker isn't starting properly!
You don't have your multi-instance broker properly configured on properly configured hardware.
Did you make sure that you are using a supported shared file system - i.e. NFS v4 not NFS v3? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 26, 2012 8:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
None of which has to do with the problem at hand. |
|
| Back to top |
|
|
| ganesh |
| Posted: Tue Jun 26, 2012 8:27 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| mqjeff wrote: |
Oh look! Real Data! That indicates that the Broker isn't starting properly!
You don't have your multi-instance broker properly configured on properly configured hardware.
Did you make sure that you are using a supported shared file system - i.e. NFS v4 not NFS v3? |
We are using NFS v4 |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jun 26, 2012 8:28 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
obtainHALock () is not able to obtain a lock on the mqbrkrs semaphore because mqm's primary group is mqm and not mqbrkrs. Change the service Id to start broker. Also, any user who issues mqsi commands to the broker must sudo to the service Id first.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
