BPM/WAS correlation error filling up the log.

Document ID : KB000004634
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

 The below log error is filling up the Agent log:

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

Environment:
Introscope Java Agent 9.5, 9.6 and 9.7 Websphere 8.0 and 8.5.5
Cause:

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.

Resolution:

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: com.ibm.bpe.framework.navigation.NavigationWorkObject4WorkMgrThread run ThreadExecutionTracer "NavigationWork"


Comment the below entry for BPM 8.x:
#TraceOneMethodWithParametersOfClass: com.ibm.bpe.framework.navigation.NavigationWorker doWork ThreadCreationTracer "Navigation-Work"


Uncomment the below entry for BPM 8.x:
TraceOneMethodWithParametersOfClass: com.ibm.bpe.framework.navigation.NavigationWorker doWork ThreadCreationTracer80 "Navigation-Work"