search cancel

No non-null parameter found

book

Article ID: 215608

calendar_today

Updated On:

Products

APM

Issue/Introduction

 
 

APM 10.7 agent monitoring SOI

[ERROR] [IntroscopeAgent.com.wily.introscope.agent.trace.correlation.jms.JMSOutgoingCorrelationTracer] No non-null parameter found that is assignable to javax.jms.Message for method: send

[ERROR] [IntroscopeAgent.com.wily.introscope.agent.trace.correlation.jms.JMSOutgoingCorrelationTracer] No non-null parameter found that is assignable to org.apache.activemq.ActiveMQMessageProducer for method: send

There are Unknown metrics in Frontends and Backends Messaging Services

Cause

 

The logs indicate that the org.apache.activemq.ActiveMQMessageProducer.send() method was instrumented with the JMSOutgoingCorrelationTracer, but its invocation didn't have a non-null message object that the JMSOutgoingCorrelationTracer would expect for the insertion of a correlation ID.

This could be due to the application implementation not providing a message object upon calling this send() method. 

 

This does not appear to be the direct culprit for the "unknown" metric names, it can be another symptom of potentially unexpected or incompatible API calls in the monitored application. 

It is worth looking for error metrics being reported around those periods to see if a genuine error is reported.

Environment

Release : 10.7.0

Component : APM Agents

Resolution

 
 

Error message being changed from ERROR to WARN

This scenario was detected and logged as a warning instead of an error since it was handled as not applicable for trace correlation with no impact to the actual metric reporting. 

The cause of unknown metrics is being investigated separately.