Hi,
Essentially this is my first run on integration between CQ5.6.1 and AppDynamics locally worked very nicely(windows env).
Performed the same steps in my local linux env and received following message : Could not start Java Agent because unable to determine Tier Name or Node Name
Full log:
Install Directory resolved to[/opt/AppDynamics/JavaAgent]
[INFO]: JavaAgent - Using Java Agent Version [Server Agent v3.7.12.0 GA #2013-11-25_16-18-41 r${env.SVN_REVISION} 587-3.7.12]
[INFO]: JavaAgent - Running IBM Java Agent [No]
[INFO]: AgentInstallManager - AppDynamics Agent edition [standard]
[INFO]: AgentInstallManager - Full Agent Registration Info Resolver is running
[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using application name [MyApp]
[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using tier name [unknown]
[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using node name [unknown]
[INFO]: AgentInstallManager - Full Agent Registration Info Resolver finished running
[INFO]: AgentInstallManager - Agent runtime directory set to [/opt/AppDynamics/JavaAgent]
[INFO]: AgentInstallManager - Agent node directory set to [unknown]
Could not start Java Agent because unable to determine Tier Name or Node Name
Agent Logging Directory [/opt/AppDynamics/JavaAgent/logs/unknown]
( I already tried to use -Dappdynamics.agent.tierName avd -Dappdynamics.agent.nodeName)
How should I set up tierName and nodeName ?
Thanks,
Peter
Hi Peter,
Can you pass the tier and node details in xml elements tier-name and node-name in /opt/AppDynamics/JavaAgent/conf/controller-info.xml file? and restart the server after making suggested changes and see how it goes?
Ex:
before update in controller-info.xml file:
<application-name>MyApp</application-name>
<tier-name></tier-name>
<node-name></node-name>
after update:
<application-name>MyApp</application-name>
<tier-name>mytier1</tier-name>
<node-name>mynode1</node-name>
Or you can start the server with additional parameter "=uniqueID" as follows, that should also helps:
-javaagent:/opt/AppDynamics/JavaAgent/javaagent.jar=uniqueID=mytier1
It might be the case that -D jvm args passed with tier and node name are not picking up as part of the startup jvm args.
Let us know how it goes after making suggested changes.
Regards,
Arun