Exception Error in Weblogic Introscope Agent log: [ERROR] [IntroscopeAgent.Agent] IntervalHeartbeat.execute threw executing: Memory Model Behaviorjava.lang.IndexOutOfBoundsException: Index: 8, Size: 8

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

Description:

We have recently installed the Introscope Agent on Weblogic application server.

We are receiving this error in Weblogic Introscope Agent log file.

[ERROR] [IntroscopeAgent.Agent] IntervalHeartbeat.execute threw executing: Memory Model Behavior
java.lang.IndexOutOfBoundsException: Index: 8, Size: 8
at
java.util.concurrent.CopyOnWriteArrayList.rangeCheck(CopyOnWriteArrayList.java:708)
at
java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:328)
at
com.wily.introscope.agent.trace.cas.APureSetTransactionElement.offerChildrenForRead(APureSetTransactionElement.java:153)
at
com.wily.introscope.agent.trace.hc2.WilyTransactionStructure.countElements(WilyTransactionStructure.java:2395)
at
com.wily.introscope.agent.trace.hc2.WilyTransactionStructure.access$300(WilyTransactionStructure.java:109)
at
com.wily.introscope.agent.trace.hc2.WilyTransactionStructure$CountTransactionStructureElementsBehavior.ITimestampedRunnable_execute(WilyTransactionStructure.java:316)
at
com.wily.util.heartbeat.IntervalHeartbeat$BehaviorNode.execute(IntervalHeartbeat.java:972)
at
com.wily.util.heartbeat.IntervalHeartbeat.executeNextBehaviorAndCalculateSleepTime(IntervalHeartbeat.java:491)
at
com.wily.util.heartbeat.IntervalHeartbeat.access$2(IntervalHeartbeat.java:445)
at
com.wily.util.heartbeat.IntervalHeartbeat$HeartbeatRunnable.run(IntervalHeartbeat.java:668)
at
java.lang.Thread.run(Thread.java:595)

How can we correct this problem?

Solution:

We have following information with regards to this Exception.

According to our Engineering Team, this exception is thrown when the list on which we are performing operations gets shrunk in thread unsafe code.

This exception is expected in the code. However, in APM release 9.1 it is not handled properly and hence is logged in the Introscope Agent log.

The problem has been fixed in Introscope release 9.5.1.0.