APM 10.7 Java Agent - Help with TT heap objects.
search cancel

APM 10.7 Java Agent - Help with TT heap objects.


Article ID: 232801


Updated On:


CA Application Performance Management (APM / Wily / Introscope)


We are utilizing a Java agent on a Mule ESB 3 server.   The vendor has called out a suspicious number of objects in the heap.I need clarification and possible help with this. 


We are using a small variety of agent versions but this particular issue relates to  21.1 with extension Bundle: muleesb:

java version "1.8.0_202"

Java(TM) SE Runtime Environment (build 1.8.0_202-b08)

Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)


 We saw that before, a full GC there is a high amount of objects of class com.wily.introscope.spec.server.transactiontrace.TransactionComponentData

It went from 

2,591,488 objects to 157,738 objects. 


Do these objects hold onto references that could be building heap size?  Are these numbers large and are TT changes warranted?





Release : 10.7.0

Component :


According to the histogram, looks like they are holding onto the objects.  But this could be due to too many TT's being generated.


To turn off Sampled

# Uncomment to disable Transaction Tracer Sampling.
# Changing this property does not require restarting the Monitored Process


To turn off cross process