MQ Access Errors due to APM agent
search cancel

MQ Access Errors due to APM agent

book

Article ID: 136113

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE

Issue/Introduction



APM Wily Agent is running on Websphere platform. Getting errors on MQ side. 

IBM support says that these errors are happening because APM is connecting to MQ. 

The agent is running with WASADMIN. 


07/03/19 10:20:05 - Process(33031.5072) User(TestMQ1) Jobname(424863/TestMQ1/BroadcomMQ  )

                    Host(I5ITEST2C.GA.Broadcom.COM)                                     

                    VRMF(8.0.0.11) QMgr(BCSYS8C)                                 

                                                                                  

AMQ8077: Entity 'WASADMIN' has insufficient authority to access object 'BCSYS8C'.

                                                                                  

EXPLANATION:                                                                      

                                                                                  

  Cause . . . . . :   The specified entity is not authorized to access the        

required object. The following requested permissions are unauthorized: inq        

  Recovery  . . . :   Ensure that the correct level of authority has been set     

for this entity against the required object, or ensure that the entity is a       

member of a privileged group.                                                     

  Technical Description . . . . . . . . :   None.                                 


Environment

Release :

Component : APM Agents

Cause

The Agent profile is using the webspheremq.pbl 


introscope.autoprobe.directivesFile=websphere-typical.pbl,hotdeploy,webspheremq.pbl


Also these MQ properties are enabled on the MQAgent properties.

 with no values are assigned. 


mqmonitor.mqagent.id.list =

handshake.mqagent.id =


mq.autodiscovery.enabled=false



Resolution

1. Remove webspheremq.pbl under :


introscope.autoprobe.directivesFile=websphere-typical.pbl,hotdeploy,webspheremq.pbl


2. Disable these properties by commenting: 

mqmonitor.mqagent.id.list =

handshake.mqagent.id =

mq.autodiscovery.enabled=false


3. App Restart is required