Seeing these repeated messages in 10.5.1.8 agent AutoProbe.log during instrumentation when tracer /com/wily/introscope/agent/trace/CrossProcessCorrelationEjbTracer is invoked:
Duplicate tracer found @ /u00/agents/javaagent/wily/core/config/j2ee.pbd; line 312 of tracer @ /u00/agents/javaagent/wily/core/config/apm-common.pbd; line 206
ejbCreate:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/CrossProcessCorrelationEjbTracer
Line 312 of j2ee.pbd is: TraceComplexMethodsIfFlagged: MessageDrivenBean3Tracing CorTracer "CorId"
Line 206 of apm-common.pbd is: TraceComplexMethodsIfFlagged: MessageDrivenBean3Tracing CorPreTracer "CorId"
In j2ee.pbd ("EJB Tracer Class Mappings") CrossProcessCorrelationEjbTracer is mapped to Tracer name CorTracer:
SetTracerClassMapping: CorTracer com.wily.introscope.agent.trace.CrossProcessCorrelationEjbTracer
In apm-common.pbd ("Correlation pre-tracers") CrossProcessCorrelationEjbTracer is mapped to Tracer name CorPreTracer:
SetTracerClassMapping: CorPreTracer com.wily.introscope.agent.trace.CrossProcessCorrelationEjbTracer
APM 9.x, 10.x
The messages can be ignored and just indicate that the same probe CrossProcessCorrelationEjbTracer has been mapped twice to tracer group MessageDrivenBean3Tracing via the different tracer names CorTracer & CorPreTracer.
The exact line numbers and tracer mappings in j2ee.pbd & apm-common.pbd may vary across APM releases e.g. Community thread: