[ERROR] A problem occurred while attempting to Introscope-enable
search cancel

[ERROR] A problem occurred while attempting to Introscope-enable

book

Article ID: 93184

calendar_today

Updated On:

Products

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

Issue/Introduction



The following message was output in the CA APM 10.5 Java Agent (JBoss) environment.
Could you tell me the cause / corrective action?
----------------------------------
[ERROR] [IntroscopeAgent.Agent] A problem occurred while attempting to Introscope-enable jdk/nashorn/internal/scripts/Script$\^eval\_: Invalid class file
[ERROR] [IntroscopeAgent.Agent] A problem occurred while attempting to Introscope-enable jdk/nashorn/internal/scripts/Script$2$\^eval\_: Invalid class file
... ...
[ERROR] [IntroscopeAgent.Agent] A problem occurred while attempting to Introscope-enable jdk/nashorn/internal/scripts/Script$4$\^eval\_: Invalid class file
----------------------------------

Environment

Release:
Component: WLYAPM

Resolution

"Nashorn" is included in the error message.
The Nashorn engine generates classes with class names that do not conform with the java spec for Identifiers 
only letters, digits and '_' are allowed, no '$', '-', '^', 

The ^(caret), \(backslash) is an invalid character for a Java class name. Per Java specifications, you cannot use an open. 
When Introscope encounters classes with invalid class names, it will not instrument them and reports an error message in the agent log.It is not possible to address this because the name is violating Java specifications.As a workaround, try adding a skipclass or skippackage statement to the Autoprobe. 
SkipPackagePrefix: jdk.nashorn.internal.

Please refer to KB000048154.
KB000048154 (Invalid class file errors occur in agent logs when the class file name contains an invalid character.