search cancel

High Concurrency Stall Feature java.lang.ClassCastException error thrown in Agent logs.


Article ID: 35705


Updated On:


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


We are seeing below error logged continuously in Agent logs, what is causing this and how can it be addressed ?

[ERROR] [IntroscopeAgent.Agent] IntervalHeartbeat.execute threw executing: High Concurrency Stall Feature 

java.lang.ClassCastException: com.wily.introscope.agent.blame.VirtualStack$VirtualElement incompatible with com.wily.introscope.agent.trace.InvocationData 

at com.wily.introscope.agent.feature.StallFeatureBase.checkAndDecrementStallsIfFinished( 

at com.wily.introscope.agent.feature.StallCheckBehaviorCorrect.ITimestampedRunnable_execute( 

at com.wily.util.heartbeat.IntervalHeartbeat$BehaviorNode.execute( 

at com.wily.util.heartbeat.IntervalHeartbeat.executeNextBehaviorAndCalculateSleepTime( 

at com.wily.util.heartbeat.IntervalHeartbeat.access$2( 

at com.wily.util.heartbeat.IntervalHeartbeat$ 








-APM Java Agent running in New mode

-Version 9.1.x or higher for e.g 9.5+,9.6+,9.7+,10.x  (Up to 10.7 SP3)



Issue is caused due to agent running in *mixed* mode i.e using custom pbd's or agent extensions that are not migrated to *new* mode and are using older non-hc2 mode tracers or old agent API calls. Some sample scenarios where this issue has been observed so far:

-Customer using 9.0.x version of webservices.pbd(uses old mode tracers) with a 9.5.5 Agent running in new mode(default). 

-Custom pbd using BlamedMethodRateTracer(old mode) instead of using BlamedMethodRateTracerHC(new mode)



Ensure that the agent is not using any custom pbd's\extensions that are using old mode(pre-9.1) tracers, if yes, please remove them and work with CA Support\Services to determine best course of action including migrating them to new mode. Also see below link to get details about some common old mode tracers and their new mode equivalent.



Additional Information