| Author |
Message
|
| issac |
 Posted: Wed Dec 07, 2011 6:03 am Post subject: Another post about BIP1536S & BIP7150E... Sorry |
 |
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
Hello,
I'm getting the following message in syslog after bar deployment.
My CM and BK are located on two hosts. CM uses aaaadmin as its service id, and MQAAAMGR as its QMGR, and BK uses mbadmin as its service id, with MQAAABK4 as its QMGR.
CM: AAACFGMGR, MQAAAMGR, aaaadmin
BK: AAABK4, MQAAABK4, mbadmin
After googling for a while, I find someone saying this is because inside MQAAABK4 mbadmin does not have enough priviledge to access its XMITQ to MQAAAMGR, which should be QL MQAAAMGR. But how could that be? mbadmin is the service id of my broker right? it's in both mqbrkrs and mqm, how could a user of group mqm does not have enough priviledge to access a local q inside?
Thanks in advance.
Dec 3 20:42:45 ASESB1 user:info WebSphere Broker v6001[680060]: (AAACFGMGR)[3599]BIP1536S: The Configuration Manager was unable to register for internal subscriptions with broker AAABK4. :
AAACFGMGR.agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 686: BrokerManager.resolveRegSub: AAACFGMGR: AAACFGMGR
Dec 3 20:42:46 ASESB1 user:info WebSphere Broker v6001[680060]: (AAACFGMGR)[3599]BIP2086E: Broker AAABK4 could only process parts of the internal configuration message. :
AAACFGMGR.agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 711: BrokerManager.logLogEntry: AAACFGMGR: AAACFGMGR
Dec 3 20:42:46 ASESB1 user:info WebSphere Broker v6001[680060]: (AAACFGMGR)[3599]BIP4046E: Invalid configuration message. See the following messages for details of the error. :
AAACFGMGR.agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 633: BrokerManager.logLogEntry: AAACFGMGR: AAACFGMGR
Dec 3 20:42:46 ASESB1 user:info WebSphere Broker v6001[680060]: (AAACFGMGR)[3599]BIP2230E: Error detected whilst processing a message in node 'DynamicSubscriptionEngine'. :
AAACFGMGR.agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 686: BrokerManager.logLogEntry: AAACFGMGR: AAACFGMGR
Dec 3 20:42:46 ASESB1 user:info WebSphere Broker v6001[680060]: (AAACFGMGR)[3599]BIP7150E: User id 'SYSTEM.BROKER.ADMIN.REPLY' not authorized to put to queue 'MQAAAMGR' on queue manager 'User not authorized to put to queue' using accounting token 'gspadmin'. : AAACFGMGR.agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 711: BrokerManager.logLogEntry: AAACFGMGR: AAACFGMG
_________________
Bazinga! |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Dec 07, 2011 11:36 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Dec 07, 2011 12:27 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
| Version 6 is no longer supported. You should upgrade to version 8. |
So you have moved your Production systems to V8 already then?
Give the poor guy a chance. Us mere mortals don't even have the V8 software yet.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 07, 2011 12:28 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| smdavies99 wrote: |
| lancelotlinc wrote: |
| Version 6 is no longer supported. You should upgrade to version 8. |
So you have moved your Production systems to V8 already then?
Give the poor guy a chance. Us mere mortals don't even have the V8 software yet. |
It doesn't GA until Friday, so. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 07, 2011 12:38 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| Version 6 is no longer supported. You should upgrade to version 8. |
Aside from raising my eyebrow at your suggestion the OP should upgrade to software that, if you already have it, gives new resonance to the phrase "early adopter", I feel I should clarify that version 6.0 is out of support; v6.1 is still supported and no end of support date has been announced.
Though clearly v6.1 is in its golden years & those still using it should think carefully about future strategies.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 07, 2011 12:43 pm Post subject: Re: Another post about BIP1536S & BIP7150E... Sorry |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| issac wrote: |
| CM uses aaaadmin as its service id, and MQAAAMGR as its QMGR, and BK uses mbadmin as its service id, with MQAAABK4 as its QMGR. |
| issac wrote: |
| Dec 3 20:42:46 ASESB1 user:info WebSphere Broker v6001[680060]: (AAACFGMGR)[3599]BIP7150E: User id 'SYSTEM.BROKER.ADMIN.REPLY' not authorized to put to queue 'MQAAAMGR' on queue manager 'User not authorized to put to queue' using accounting token 'gspadmin'. : AAACFGMGR.agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 711: BrokerManager.logLogEntry: AAACFGMGR: AAACFGMG |
Also even if you can't upgrade you should be on the latest maintenance of what you're using.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| issac |
| Posted: Wed Dec 07, 2011 5:29 pm Post subject: |
|
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
Hello, guys
This system is a victim of bureacracy here... It's not my decision not to upgrade or install a fix... I believe I hate this version more than anyone of you.
Besides the version, anyone familiar with a solution to BIP1536S & BIP7150E?
_________________
Bazinga! |
|
| Back to top |
|
|
|
|
