search cancel

iib-ia-dd040260-11.1.4.29 issue

book

Article ID: 188265

calendar_today

Updated On:

Products

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

Issue/Introduction

I am upgrading MQ Monitor from IIB10Fieldpack to iib-ia-dd040260-11.1.4.29. I went through the instructions here and had MQ admin confirm that all the necessary rights are set.

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/dx-apm-saas/SaaS/implementing-agents/infrastructure-agent/IIB-Monitoring.html

Yet, I see the following error on startup 

[INFO] [IntroscopeAgent.iib-ia] start monitoring DBRKRB2  as initial connection is successful

[INFO] [IntroscopeAgent.iib-ia] BrokerTracer thread started.

[INFO] [IntroscopeAgent.iib-ia] Execution group Tracer thread started.

[ERROR] [IntroscopeAgent.iib-ia] Connection to jms broker queue manager is failed; presence of jms queues cannot be verified. Make sure jms connection parameters are correct and jms queue manger is up and running. 

[ERROR] [IntroscopeAgent.iib-ia] Message Flow performance statistics and Broker performance statistics will not be reported by IIB Monitor.

[ERROR] [IntroscopeAgent.iib-ia] MQJE001: Completion Code '2', Reason '2035'.

com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2035'.

        at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:250)

        at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:450)

        at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:487)

        at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:97)

        at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:194)

        at com.ibm.mq.MQQueueManagerFactory.obtainBaseMQQueueManager(MQQueueManagerFactory.java:868)

        at com.ibm.mq.MQQueueManagerFactory.procure(MQQueueManagerFactory.java:816)

        at com.ibm.mq.MQQueueManagerFactory.constructQueueManager(MQQueueManagerFactory.java:758)

        at com.ibm.mq.MQQueueManagerFactory.createQueueManager(MQQueueManagerFactory.java:200)

        at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:727)

        at com.ca.apm.agent.extension.iib.mbmonitor.JMSQueueValidator.init(JMSQueueValidator.java:419)

        at com.ca.apm.agent.extension.iib.mbmonitor.MBTreeConfigMain.getMQStatistics(MBTreeConfigMain.java:66)

        at com.ca.apm.agent.extension.iib.mbmonitor.MBTreeConfigMain.startTracers(MBTreeConfigMain.java:141)

        at com.ca.apm.agent.extension.iib.mbmonitor.MBTreeConfigMain.start(MBTreeConfigMain.java:117)

        at com.ca.apm.agent.extension.iib.Invoker.call(Invoker.java:45)

        at com.ca.apm.agent.extension.iib.Invoker.access$0(Invoker.java:44)

        at com.ca.apm.agent.extension.iib.Invoker$1.run(Invoker.java:76)

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

        at java.lang.Thread.run(Thread.java:748)

[INFO] [IntroscopeAgent.iib-ia] Integration Node (Message Broker) monitoring has started.

[INFO] [IntroscopeAgent.MQMonitor] Connection is successful using channel TRP.WILY.SVRCONN

[INFO] [IntroscopeAgent.MQMonitor] Start Monitoring: namelist at dimq12:15010

 

Environment

Release : 11.1.0

Component : APM Agents

Cause

IA install script changes agent profile file owner/mode back to root, causing failure for non-root user.

Resolution

- Fixed the IA install script.  When installing as non-root user, the Agent profile will now be updated with current user as the owner.

- Will include the fix in the next release.