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

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to run java agent on WebSphere

SOLVED
Highlighted

Unable to run java agent on WebSphere

I'm running a:

WebSphere Application Server 8.5.5.13

AppDynamics Controller build 4.5.0.25224

AppServerAgent-ibm-4.5.0.23604

 

For some reason, the agent is not able to start and disable itself.

 

I have followed the instructions to configure a Java agent https://docs.appdynamics.com/display/PRO45/Java+Agent

Also, I have followd the step to configure the websphere settings. https://docs.appdynamics.com/display/PRO44/IBM+WebSphere+and+InfoSphere+Startup+Settings

 

This is the configuration from the controller-info.xml:

<?xml version="1.0" encoding="UTF-8"?>
<controller-info>
 <controller-host>10.53.217.182</controller-host>
 <controller-port>8090</controller-port>
 <controller-ssl-enabled>false</controller-ssl-enabled>
 <application-name>PlantsByWebSphere</application-name>
 <tier-name>InventoryTier</tier-name>
 <node-name>dxceis05_nodes</node-name>
 <agent-runtime-dir></agent-runtime-dir>
 <enable-orchestration>false</enable-orchestration>
 <account-name>controllerAdmin</account-name>
 <account-access-key></account-access-key>
 <force-agent-registration>false</force-agent-registration>
</controller-info>

 

This is the log from the agent:

[Thread-3] 06 Aug 2018 17:54:00,650  INFO JavaAgent - All agent classes have been pre-loaded
[Thread-3] 06 Aug 2018 17:54:00,655  INFO AgentKernel - Starting Java Agent at Mon Aug 06 17:54:00 CDT 2018 ...
[Thread-3] 06 Aug 2018 17:54:00,655  INFO AgentKernel - Time zone: Central Standard Time
[Thread-3] 06 Aug 2018 17:54:00,680  INFO XMLConfigManager - Orchestration is disabled - disabling virtualization resolvers by default.
[Thread-3] 06 Aug 2018 17:54:00,694  INFO XMLConfigManager - Default Host Identifier Resolver using host name for unique host identifier [test]
[Thread-3] 06 Aug 2018 17:54:00,695  INFO XMLConfigManager - Default IP Address Resolver found IP addresses [[10.53.217.172, 10.54.218.172]]
[Thread-3] 06 Aug 2018 17:54:00,697  INFO XMLConfigManager - Full Agent Registration Info Resolver using selfService [false]
[Thread-3] 06 Aug 2018 17:54:00,701  INFO XMLConfigManager - Full Agent Registration Info Resolver using selfService [false]
[Thread-3] 06 Aug 2018 17:54:00,701  INFO XMLConfigManager - Full Agent Registration Info Resolver using application name [PlantsByWebSphere]
[Thread-3] 06 Aug 2018 17:54:00,701  INFO XMLConfigManager - Full Agent Registration Info Resolver using tier name [InventoryTier]
[Thread-3] 06 Aug 2018 17:54:00,701  INFO XMLConfigManager - Full Agent Registration Info Resolver using node name [test_nodes]
[Thread-3] 06 Aug 2018 17:54:00,703  INFO XMLConfigManager - XML Controller Info Resolver found controller host [10.53.217.182]
[Thread-3] 06 Aug 2018 17:54:00,703  INFO XMLConfigManager - XML Controller Info Resolver found controller port [8090]
[Thread-3] 06 Aug 2018 17:54:00,707  WARN XMLConfigManager - XML Controller Info Resolver found invalid controller host information [] in controller-info.xml; Please specify a valid value if it
is not already set in system properties.
[Thread-3] 06 Aug 2018 17:54:00,707  WARN XMLConfigManager - XML Controller Info Resolver found invalid controller port information [] in controller-info.xml; Please specify a valid value if it
is not already set in system properties.
[Thread-3] 06 Aug 2018 17:54:00,709  INFO XMLConfigManager - XML Agent Account Info Resolver using account name [controllerAdmin]
[Thread-3] 06 Aug 2018 17:54:00,712  WARN XMLConfigManager - XML Agent Account Info Resolver did not find account access key.
[Thread-3] 06 Aug 2018 17:54:00,725 ERROR JavaAgent - Could Not Start Java Agent, Disabling !!!!!
com.singularity.ee.agent.appagent.kernel.spi.c: Could not initialize configuration
        at com.singularity.ee.agent.appagent.kernel.m.start(m.java:115) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd relea
se/4.5.0-release]
        at com.singularity.ee.agent.appagent.kernel.JavaAgent.initialize(JavaAgent.java:553) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2
d0824499a2c23dd release/4.5.0-release]
        at com.singularity.ee.agent.appagent.kernel.JavaAgent.initialize(JavaAgent.java:329) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2
d0824499a2c23dd release/4.5.0-release]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) ~[?:1.8.0]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) ~[?:1.8.0]
        at java.lang.reflect.Method.invoke(Method.java:508) ~[?:1.8.0]
        at com.singularity.ee.agent.appagent.AgentEntryPoint$1.run(AgentEntryPoint.java:655) ~[?:Server IBM Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d082449
9a2c23dd release/4.5.0-release]
Caused by: com.singularity.ee.agent.configuration.a: Could not resolve agent-controller basic configuration
        at com.singularity.ee.agent.appagent.kernel.config.xml.d.a(d.java:204) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23d
d release/4.5.0-release]
        at com.singularity.ee.agent.appagent.kernel.config.xml.d.<init>(d.java:170) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a
2c23dd release/4.5.0-release]
        at com.singularity.ee.agent.appagent.kernel.m.start(m.java:112) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd relea
se/4.5.0-release]
        ... 7 more

There is connectivity between the agent and the controller.

The websphere doesn't have security.

The controller is not set up to use SSL.

 

Any idea what I could be doing wrong?

 

Thanks

Unable to run java agent on WebSphere
2 REPLIES 2
AppDynamics Team

Re: Unable to run java agent on WebSphere

Hi Daniel,

It seems you are missing some information on the controller-info.xml, you need to put the account name and the account access key. That info is available on the license menu on the gear icon of your controller.

 

JC



Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.

Re: Unable to run java agent on WebSphere

I found it after a while that the access-key was missing.

 

I tried to follow the tutorials, but I think they were not clear enough for me.