Could Not Start WebSphere Java Agent

CommunityUser — Mon, 06 Aug 2018 19:38:37 GMT

Hi, I'm new to appDynamics. I'm trying to configure a WebSphere agent. Its a new websphere 8.5.5.13 installation with just a test application installed.

I followed all the instructions and I saw with the ps -ef that the javaagent.jar is being launched.

https://docs.appdynamics.com/display/PRO45/Install+the+Java+Agent

https://docs.appdynamics.com/display/PRO45/IBM+WebSphere+and+InfoSphere+Startup+Settings

But I got this error.

[Thread-3] 06 Aug 2018 13:52:52,732  INFO JavaAgent - Logging set up for log4j2
[Thread-3] 06 Aug 2018 13:52:52,732  INFO JavaAgent - ####################################################################################
[Thread-3] 06 Aug 2018 13:52:52,732  INFO JavaAgent - Java Agent Directory [/usr/local/appdynamics/appagent/ver4.5.0.23604]
[Thread-3] 06 Aug 2018 13:52:52,732  INFO JavaAgent - Java Agent AppAgent directory [/usr/local/appdynamics/appagent/ver4.5.0.23604]
[Thread-3] 06 Aug 2018 13:52:52,732  INFO JavaAgent - Using Java Agent Version [Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release]
[Thread-3] 06 Aug 2018 13:52:52,732  INFO JavaAgent - All agent classes have been pre-loaded
[Thread-3] 06 Aug 2018 13:52:52,738  INFO AgentKernel - Starting Java Agent at Mon Aug 06 13:52:52 CDT 2018 ...
[Thread-3] 06 Aug 2018 13:52:52,738  INFO AgentKernel - Time zone: Central Standard Time
[Thread-3] 06 Aug 2018 13:52:52,763  INFO XMLConfigManager - Orchestration is disabled - disabling virtualization resolvers by default.
[Thread-3] 06 Aug 2018 13:52:52,780  INFO XMLConfigManager - Default Host Identifier Resolver using host name for unique host identifier [test_was]
[Thread-3] 06 Aug 2018 13:52:52,781  INFO XMLConfigManager - Default IP Address Resolver found IP addresses [[10.56.219.172, 10.57.19.172]]
[Thread-3] 06 Aug 2018 13:52:52,785  INFO XMLConfigManager - Full Agent Registration Info Resolver using selfService [false]
[Thread-3] 06 Aug 2018 13:52:52,789  INFO XMLConfigManager - Full Agent Registration Info Resolver using selfService [false]
[Thread-3] 06 Aug 2018 13:52:52,789  INFO XMLConfigManager - Full Agent Registration Info Resolver using application name [Plants App]
[Thread-3] 06 Aug 2018 13:52:52,789  INFO XMLConfigManager - Full Agent Registration Info Resolver using tier name [Plants Frontend]
[Thread-3] 06 Aug 2018 13:52:52,789  INFO XMLConfigManager - Full Agent Registration Info Resolver using node name [was_nodes]
[Thread-3] 06 Aug 2018 13:52:52,793  INFO XMLConfigManager - XML Controller Info Resolver found controller host [controller_server]
[Thread-3] 06 Aug 2018 13:52:52,793  INFO XMLConfigManager - XML Controller Info Resolver found controller port [8090]
[Thread-3] 06 Aug 2018 13:52:52,798  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 13:52:52,798  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 13:52:52,813  INFO XMLConfigManager - XML Agent Account Info Resolver did not find account name. Using default account name [customer1]
[Thread-3] 06 Aug 2018 13:52:52,813  WARN XMLConfigManager - XML Agent Account Info Resolver did not find account access key.
[Thread-3] 06 Aug 2018 13:52:52,826 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 release/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 r88b53d319a45abc58963be9d2d0824499a2c23dd 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 r88b53d319a45abc58963be9d2d0824499a2c23dd 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 r88b53d319a45abc58963be9d2d0824499a2c23dd 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 r88b53d319a45abc58963be9d2d0824499a2c23dd 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 r88b53d319a45abc58963be9d2d0824499a2c23dd 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 release/4.5.0-release]
        ... 7 more

I saw on the log "Could not resolve agent-controller basic configuration". But I followed all the steps, I'm not sure what it means.

Re: Could Not Start WebSphere Java Agent

CommunityUser — Fri, 17 Aug 2018 09:39:48 GMT

Hi Daniel.Blanco

you still have to specify the account access key:

[Thread-3] 06 Aug 2018 13:52:52,813  WARN XMLConfigManager - XML Agent Account Info Resolver did not find account access key.

Thanks

Philipp

Re: Could Not Start WebSphere Java Agent

CommunityUser — Fri, 17 Aug 2018 12:32:18 GMT

Thanks, I put the access key and started working.

Shouldn't that be an error instead of a warining?

topic Could Not Start WebSphere Java Agent in Splunk AppDynamics

Could Not Start WebSphere Java Agent

Re: Could Not Start WebSphere Java Agent

Re: Could Not Start WebSphere Java Agent