Java Agent - Websphere Base/Core/Liberty - Confirmation of config settings for non IBM J9 for memory leak issue using Agent.jar
search cancel

Java Agent - Websphere Base/Core/Liberty - Confirmation of config settings for non IBM J9 for memory leak issue using Agent.jar

book

Article ID: 394353

calendar_today

Updated On: 04-15-2025

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

Java Agent - Websphere Base/Core/Liberty - Confirmation of config settings for non IBM J9 for memory leak issue using Agent.jar

To resolve the memory leak issue with Agent.jar for IBM J9, the fix was to add the below config settings in the IntroscopeAgent.profile file to resolve the Class Loader leak issue: 

introscope.agent.deep.entrypoint.enabled=false

introscope.agent.automatic.backend.detection.enabled=false

introscope.agent.deep.instrumentation.visibility.processor.enabled=false

Can we use the same settings for any non-IBM J9 JVMs and this will also work?

Resolution

Suppose that the non-IBM K9 JVM has a memory leak on repeated class redefinition. If so, the disabling of these features would have no effect on memory consumption.

Disabling those settings would work in the sense that they would disable entry/exit point detection.