APMIA - Error in log with Mainframe extension

Products

• DX Application Performance Management

Issue/Introduction

Below exception is flooding the APMIA logs.  Exception indicates DB2 is enabled but I have disabled it in the bundle.properties file of the mainframe extension and restarted.

# Changing this property requires restarting the Monitored Process
#introscope.agent.mainframe.CICS.Transaction.Trace.DB2=yes

 

[ERROR] [IntroscopeAgent.Mainframe] Metric Poll Executor-0 -> Exception encountered when trying to invoke Insight REST CALL.

 

java.net.ConnectException: Failed to connect to <hostname>/<IP address>:<port>

 

at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.kt:285)

.

.

.

.

at com.ca.apm.agent.extension.mainframe.metrics.rest.InsightRestClient.getResponse(InsightRestClient.java:135)

 

at com.ca.apm.agent.extension.mainframe.metrics.rest.InsightRestClient.processGetRequest(InsightRestClient.java:49)

 

at com.ca.apm.agent.extension.mainframe.metrics.rest.InsightRestClient.getAgents(InsightRestClient.java:113)

 

at com.ca.apm.agent.extension.mainframe.metrics.insight.model.InsightMetricCategoryModel.queryAgents(InsightMetricCategoryModel.java:43)

 

at com.ca.apm.agent.extension.mainframe.metrics.processor.InsightRestEndpointConsumer.getDB2AgentMap(InsightRestEndpointConsumer.java:158)

 

at com.ca.apm.agent.extension.mainframe.metrics.processor.InsightRestEndpointConsumer.getDB2List(InsightRestEndpointConsumer.java:148)

 

at com.ca.apm.agent.extension.mainframe.metrics.processor.InsightRestEndpointConsumer.ingest(InsightRestEndpointConsumer.java:73)

 

at com.ca.apm.agent.extension.mainframe.metrics.processor.InsightRestMetricProcessor.process(InsightRestMetricProcessor.java:45)

 

at com.ca.apm.agent.extension.mainframe.metrics.InsightProcessorTask.run(InsightProcessorTask.java:30)

 

 

Caused by: java.net.ConnectException: Connection refused: no further information

 

at java.base/sun.nio.ch.Net.pollConnect(Native Method)

 

Resolution

By default, the introscope.agent.mainframe.CICS.Transaction.Trace.DB2 property is set to yes.  If you comment it out, the parser will default the "yes" value.

To disable DB2 metrics, enable (remove the # character) and explicitly set the property to no as below and restart the APMIA Agent.

introscope.agent.mainframe.CICS.Transaction.Trace.DB2=no