ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

BPM/WAS correlation error filling up the log.


Article ID: 4634


Updated On:


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


 The below log error is filling up the Agent log:

 [ERROR] [IntroscopeAgent.Agent] ThreadCreationTracer: enginemessagewrapper is null


This issue only happens when using WPS.pbd.

This is a configuration problem. In case of BPM/WAS 8x, use a different Thread Correlation Tracer. This is mentioned in the PBD as well as the code.


Introscope Java Agent 9.5, 9.6 and 9.7 Websphere 8.0 and 8.5.5


Under your WPS.pbd, make the following changes:

Comment the below entry for BPM 8.x:

#SetTracerClassMapping:  ThreadCreationTracer com.wily.powerpack.websphereprocserver.tracer.ThreadCreationTracer com.wily.introscope.probebuilder.validate.ResourceNameValidator
#Uncomment the below entry for BPM 8.x
SetTracerClassMapping:  ThreadCreationTracer80 com.wily.powerpack.websphereprocserver.tracer.ThreadCreationTracer80 com.wily.introscope.probebuilder.validate.ResourceNameValidator

TraceOneMethodWithParametersOfClass: run ThreadExecutionTracer "NavigationWork"

Comment the below entry for BPM 8.x:
#TraceOneMethodWithParametersOfClass: doWork ThreadCreationTracer "Navigation-Work"

Uncomment the below entry for BPM 8.x:
TraceOneMethodWithParametersOfClass: doWork ThreadCreationTracer80 "Navigation-Work"