TEC610828: Invalid class file errors occur in agent logs when the class file name contains an invalid character

Document created by Mary_Clark Employee on May 27, 2016Last modified by J.J. Lovett on May 27, 2016
Version 2Show Document
  • View in full screen mode

Document ID:  TEC610828

Last Modified Date:  5/7/2014
Authored By: Mary_Clark

  • Products
    • CA Application Performance Management
  • Components
    • APM AGENTS
    • INTROSCOPE

 

Description:Invalid class file errors occur when the class file name contains an invalid character such as in the following:[ERROR] [IntroscopeAgent.Agent] A problem occurred while attempting to Introscope-enable oracle/security/jps/internal/keystore/config/jaxb/Password$JaxbAccessorM_getEncryptedPassword_setEncryptedPassword_[B: Invalid class file

 

Solution:The details on the Java specification class naming are available here:http://java.sun.com/docs/books/jls/second_edition/html/lexical.doc.html#40625

    • oracle/security/jps/internal/keystore/config/jaxb/Password$JaxbAccessorM_get
      EncryptedPassword_setEncryptedPassword_[B:Invalid class file

The "[" (square bracket) is an invalid character for a Java class name. Per Java specifications, you cannot use an open
square bracket ([) as part of a Java class file name.
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 directives:

    • Create a PBD file and add the skip directives of the classes for which you are seeing the errors:

    • SkipClass: oracle.security.jps.internal.keystore.config.jaxb.Password$JaxbAccessorM_getEncryptedPassword_setEncryptedPassword_[B

 

 

Search the Entire CA APM Knowledge Base

 

search-kb.jpg

Attachments

    Outcomes