ACE 11 agent not working, ERROR com.ibm.broker.config.proxy.ConfigManagerProxyPropertyNotInitializedException

Products

• CA Application Performance Management SaaS

Issue/Introduction

The following ERROR is reported when starting up the IIB agent:

5/11/23 07:30:59 AM BST [ERROR] [IntroscopeAgent.iib-ia] See nested Exception for more details
com.ibm.broker.config.proxy.ConfigManagerProxyPropertyNotInitializedException: See nested Exception for more details
        at com.ibm.broker.config.proxy.BrokerProxy.getExecutionGroups(BrokerProxy.java:1347)
        at com.ca.apm.agent.extension.iib.mbmonitor.tracers.ExecutionGroupTracer.reportBroker(ExecutionGroupTracer.java:491)
        at com.ca.apm.agent.extension.iib.mbmonitor.tracers.ExecutionGroupTracer.reportFlowAndBrokerMetrics(ExecutionGroupTracer.java:618)
        at com.ca.apm.agent.extension.iib.mbmonitor.tracers.ExecutionGroupTracer.run(ExecutionGroupTracer.java:592)
        at java.lang.Thread.run(Thread.java:825)
5/11/23 07:30:59 AM BST [ERROR] [IntroscopeAgent.iib-ia] See nested Exception for more details
com.ibm.broker.config.proxy.ConfigManagerProxyPropertyNotInitializedException: See nested Exception for more details
        at com.ibm.broker.config.proxy.BrokerProxy.getExecutionGroups(BrokerProxy.java:1347)
        at com.ca.apm.agent.extension.iib.mbmonitor.tracers.ExecutionGroupTracer.reportBroker(ExecutionGroupTracer.java:491)
        at com.ca.apm.agent.extension.iib.mbmonitor.tracers.ExecutionGroupTracer.reportFlowAndBrokerMetrics(ExecutionGroupTracer.java:618)
        at com.ca.apm.agent.extension.iib.mbmonitor.tracers.ExecutionGroupTracer.run(ExecutionGroupTracer.java:592)
        at java.lang.Thread.run(Thread.java:825)

Environment

DX APM Infrastructure Agent 2022.1.0.25 

Cause

The issue occurs when IIB API is not able to return executiongroupproxy list for broker. 

 

To confirm if issue is this, run <brokerhost>:<brokerport> for the broker which is giving the exception. 

 

 

Check if there is a execution group that is not started

 

Run "curl <brokerhost>:<brokerport>/apiv2/servers/<stoppedserver>?depth=2 --verbose" and check the response code. If response code is not 2xx, next IIB release should fix the issue.

Resolution

Fixed in next IIB SaaS release.

 

Additional Information

IIB Monitoring/IBM ACE Monitoring