Java Agent unable to start successfully.
search cancel

Java Agent unable to start successfully.


Article ID: 32798


Updated On:


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





  APM Java Agent is not starting up and the following error is logged into the Appserver logs. In addition, no logs are being generated by the Agent.

 [ERROR] [IntroscopeAgent] A problem occurred while attempting to create the delegate agent
at com.wily.introscope.agent.AgentShim.IAgentShim_getAgent(
at com.wily.introscope.agent.AgentShim.getAgent(
at com.wily.introscope.api.instrument.JavaAgent.premain(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(
at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(


  -Oracle 1.7 JRE



  Issue was caused due to a custom extension deployed in <Wily_Home>/core/ext folder which was compiled with 1.8 JDK. However the Application Server was

 running with 1.7 JRE. As such, Java is backward compatible but not the compiled code. So code compiled with a higher version JRE cannot be run by a lower version JRE, thus causing Agent failure while trying to load the extension. Removing the extension from the ext folder addressed the startup issue.


 In general, if above error is seen and all the configuration is validated, then the likely root cause is either an Agent extension that is not compatible with JRE version used by Application Server and\or the Agent itself is compatible with JRE.


 Additional Information:

 There are number of third party tools that could be used to determine the Java version used to compile the code that could be useful in above scenario.




Release: CEMUGD00200-9.5-Introscope to CA Application-Performance Management-Upgrade Main