Java (Java Agent, Installation, JVM, and Controller Installation)

cancel
Showing results for 
Search instead for 
Did you mean: 

I installed the IBM java agent, but getting this error 'JVM getBootstrapResource not available on ClassLoader Started AppDynamics Java Agent Successfully.'

SOLVED
Highlighted
New Poster

 

Full Agent Registration Info Resolver using selfService [true]
Full Agent Registration Info Resolver using selfService [true]
Full Agent Registration Info Resolver using application name [SterlingIntegrator.DEV]
Full Agent Registration Info Resolver using tier name [B2B]
Full Agent Registration Info Resolver using node name [node]
Install Directory resolved to[/sterling/data/AppD/AppServerAgent-ibm-4.5.13.27526]
findBootstrapClass method not found
method findBootstrapClass not found for the JVM
getBootstrapResource not available on ClassLoader
Agent conf directory set to [/sterling/data/AppD/AppServerAgent-ibm-4.5.13.27526/ver4.5.13.27526/conf]
[Thread-3] Wed Sep 11 10:33:21 CDT 2019[INFO]: JavaAgent - Agent conf directory set to [/sterling/data/AppD/AppServerAgent-ibm-4.5.13.27526/ver4.5.13.27526/conf]
[Thread-3] Wed Sep 11 10:33:21 CDT 2019[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver is running
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [true]
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [true]
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using application name [SterlingIntegrator.DEV]
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using tier name [B2B]
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using node name [node]
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver finished running
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: AgentInstallManager - Agent runtime directory set to [/sterling/data/AppD/AppServerAgent-ibm-4.5.13.27526/ver4.5.13.27526]
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: AgentInstallManager - Agent node directory set to [node]
Agent runtime conf directory set to /sterling/data/AppD/AppServerAgent-ibm-4.5.13.27526/ver4.5.13.27526/conf
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: AgentInstallManager - Agent runtime conf directory set to /sterling/data/AppD/AppServerAgent-ibm-4.5.13.27526/ver4.5.13.27526/conf
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: JavaAgent - Using Java Agent Version [Server Agent #4.5.13.27526 v4.5.13 GA compatible with 4.4.1.0 r390fa71f498c037b2e0e3f9b428b0ab6e3d81522 pull-requests/2610]
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: JavaAgent - Running IBM Java Agent [Yes]
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: JavaAgent - Java Agent Directory [/sterling/data/AppD/AppServerAgent-ibm-4.5.13.27526/ver4.5.13.27526]
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: JavaAgent - Java Agent AppAgent directory [/sterling/data/AppD/AppServerAgent-ibm-4.5.13.27526/ver4.5.13.27526]
Agent logging directory set to [/sterling/data/AppD/AppServerAgent-ibm-4.5.13.27526/ver4.5.13.27526/logs]
[Thread-3] Wed Sep 11 10:33:22 CDT 2019[INFO]: JavaAgent - Agent logging directory set to [/sterling/data/AppD/AppServerAgent-ibm-4.5.13.27526/ver4.5.13.27526/logs]
Found internal config file /com/sterlingcommerce/security/jcae/provider.txt, loading it now!
Done loading it.
Running obfuscated agent
findBootstrapClass method not found
method findBootstrapClass not found for the JVM
getBootstrapResource not available on ClassLoader
Started AppDynamics Java Agent Successfully.

I installed the IBM java agent, but getting this error 'JVM getBootstrapResource not available on ClassLoader Started AppDynamics Java Agent Successfully.'
1 REPLY 1
AppDynamics Team

Hi Srikanth,

 

Thanks for reaching out to the community.

 

Regarding the message, as the agent is running as expected then you can ignore it now for the following reason.

 

[Reason]-------------------

For a JVM, there is a build-in classLoader java.lang.ClassLoader. The message indicated that there is no class loader with that name. However, JVM would run through the delegate chain of class loader to find the appropriate one during the startup.

 

Ref: https://blogs.oracle.com/sundararajan/understanding-java-class-loading

---------------------------------

 

If your node still doesn't show up on your controller, please file a help ticket in Zendesk with your logs for faster resolution of the issue.

 

Best regards,

Yusuke