Too many "Processing class com/sun/proxy/$Proxy" in Autoprobe.log

Products

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

Issue/Introduction

Java Agent Autoprobe.log contains a lot of line reporting the below message:

Processing class com/sun/proxy/$Proxy14023
Processing class com/sun/proxy/$Proxy14024
Processing class com/sun/proxy/$Proxy14025
Processing class com/sun/proxy/$Proxy14026
Processing class com/sun/proxy/$Proxy14027
Processing class com/sun/proxy/$Proxy14028
Processing class com/sun/proxy/$Proxy14029
Processing class com/sun/proxy/$Proxy14030

How can I prevent the multiple lines or disable this particular feature?

Environment

Introscope Agent 10.5.x, 10.7.x

 

Cause

The problem is caused by the use of invalid characters in the class names

See also:
https://community.broadcom.com/participate/ideation-home/viewidea?IdeationKey=632c2e56-d998-48c3-808e-26feb216c53b
https://knowledge.broadcom.com/external/article/93184/error-a-problem-occurred-while-attemptin.html
https://ca-broadcomcsm.wolkenservicedesk.com/wolken/esd/knowledgebase_search?articleId=182951

Resolution

You can try to workaround the issue by implementing 1 of the below recommendations.  You need to restart your JVM each time.

Suggestion #1 : Skip package com.sun.proxy

- Create a test.pbd with below content
SkipPackagePrefix: com.sun.proxy
- Open the core/config/IntroscopeAgent.profile, add the test.pbd to directivesFiles as below:
introscope.autoprobe.directivesFile=<yourappserver-typical/full>.pbl,hotdeploy,test.pbd


Suggestion #2 : Disable deep inheritance in the core/config/IntroscopeAgent.profile:

introscope.autoprobe.deepinheritance.enabled=false


Suggestion #3 : Disable smart instrumentation in the core/config/IntroscopeAgent.profile:

introscope.agent.deep.entrypoint.enabled=false
introscope.agent.deep.instrumentation.enabled=false
introscope.agent.deep.trace.enabled=false
introscope.agent.deep.errorsnapshot.enable=false
introscope.agent.deep.automatic.trace.crossprocess.enabled=false
introscope.agent.automatic.backend.detection.enabled=false

IMPORTANT: move or delete AutoPersist.pbd file from config/hotdeploy folder
disable EJB tracing


Suggestion #4 : Disable EJB intrumentation in the toggles-full.pbd or toggles-typical.pbd as below:

#TurnOn: EJB2StubTracing
#TurnOn: SessionBeanTracing
#TurnOn: EntityBeanTracing
#TurnOn: MessageDrivenBeanTracing
#TurnOn: EJB3StubTracing
#TurnOn: SessionBean3Tracing
#TurnOn: EntityBean3Tracing
#TurnOn: MessageDrivenBean3Tracing

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/implementing-agents/java-agent/advanced-instrumentation/probebuilder-directives.html#concept.dita_bf825fd30e0a0fa5248bfaf42e1a9aa2feaf2ed3_DefaultTracerGroupsandTogglesFiles


If the problem persists, open a support case and include the <agent-home>/logs directory + appserver logs from each of the above tests