So that was a negative on the file upload of 30+ meg. So attache the configuration(probably important), and interesting looking logs. Note that port 8181 is open in iptables, which doesn't mean that everyone can go hacking me now ![]()
Has some personality this forum
I'll try to attach some logs now...
One log perhaps...
How about some text rather:
[Thread-0] 09 Jun 2015 19:01:19,762 INFO JavaAgent - ####################################################################################
[Thread-0] 09 Jun 2015 19:01:19,762 INFO JavaAgent - Java Agent Directory [/home/apache-tomcat-7.0.42/bin/AppServerAgent-4.0.5.1/ver4.0.5.1]
[Thread-0] 09 Jun 2015 19:01:19,763 INFO JavaAgent - Java Agent AppAgent directory [/home/apache-tomcat-7.0.42/bin/AppServerAgent-4.0.5.1/ver4.0.5.1]
[Thread-0] 09 Jun 2015 19:01:19,763 INFO JavaAgent - Using Java Agent Version [Server Agent v4.0.5.1 GA #2015-05-04_14-03-30 rf7b2ac62ef1cf0f0f0e6d1ba48939514ef4b7f0e 23-4.0.5.next]
[Thread-0] 09 Jun 2015 19:01:19,763 INFO JavaAgent - All agent classes have been pre-loaded
[Thread-0] 09 Jun 2015 19:01:19,763 INFO JavaAgent - Using ASM v3.3.1
[Thread-0] 09 Jun 2015 19:01:19,765 INFO AgentKernel - Starting Java Agent at Tue Jun 09 19:01:19 CEST 2015 ...
[Thread-0] 09 Jun 2015 19:01:19,851 INFO XMLConfigManager - Orchestration is disabled - disabling virtualization resolvers by default.
[Thread-0] 09 Jun 2015 19:01:19,896 INFO XMLConfigManager - Default Host Identifier Resolver using host name for unique host identifier [ikube.be]
[Thread-0] 09 Jun 2015 19:01:19,899 INFO XMLConfigManager - Default IP Address Resolver found IP addresses [[fe80:0:0:0:21b:21ff:fe69:6da0%2, 192.168.1.42]]
[Thread-0] 09 Jun 2015 19:01:19,915 INFO XMLConfigManager - Full Agent Registration Info Resolver using selfService [true]
[Thread-0] 09 Jun 2015 19:01:19,928 INFO XMLConfigManager - Full Agent Registration Info Resolver using agent runtime dir [/home/apache-tomcat-7.0.42/bin/AppServerAgent-4.0.5.1]
[Thread-0] 09 Jun 2015 19:01:19,929 INFO XMLConfigManager - Full Agent Registration Info Resolver using selfService [true]
[Thread-0] 09 Jun 2015 19:01:19,929 INFO XMLConfigManager - Full Agent Registration Info Resolver using application name [ikube]
[Thread-0] 09 Jun 2015 19:01:19,929 INFO XMLConfigManager - Full Agent Registration Info Resolver using tier name [ikube]
[Thread-0] 09 Jun 2015 19:01:19,929 INFO XMLConfigManager - Full Agent Registration Info Resolver using node name [ikube]
[Thread-0] 09 Jun 2015 19:01:19,943 INFO XMLConfigManager - XML Controller Info Resolver found controller host [paid127.saas.appdynamics.com]
[Thread-0] 09 Jun 2015 19:01:19,944 INFO XMLConfigManager - XML Controller Info Resolver found controller port [443]
[Thread-0] 09 Jun 2015 19:01:19,958 INFO XMLConfigManager - XML Controller Info Resolver found controller host [ikube.be]
[Thread-0] 09 Jun 2015 19:01:19,958 INFO XMLConfigManager - XML Controller Info Resolver found controller port [8181]
[Thread-0] 09 Jun 2015 19:01:19,972 INFO XMLConfigManager - XML Agent Account Info Resolver using account name [IkubeLtd]
[Thread-0] 09 Jun 2015 19:01:19,972 INFO XMLConfigManager - XML Agent Account Info Resolver using account access key [quf23mgu4vn6]
[Thread-0] 09 Jun 2015 19:01:19,975 INFO XMLConfigManager - Configuration Channel is using ControllerInfo:: host:[paid127.saas.appdynamics.com] port:[443] sslEnabled:[true] keystoreFile:[] validation:[UNSPECIFIED]
[Thread-0] 09 Jun 2015 19:01:19,975 INFO XMLConfigManager - Keystore file was not found
[Thread-0] 09 Jun 2015 19:01:20,247 INFO XMLConfigManager - Trying secure protocol:TLSv1.2
[Thread-0] 09 Jun 2015 19:01:20,466 INFO AgentConfigWatchdog - Agent overwrite set to false
[Thread-0] 09 Jun 2015 19:01:20,472 INFO AgentConfigWatchdog - Parsed 2 filters from <sensitive-data-filters> section
[Thread-0] 09 Jun 2015 19:01:20,502 INFO XMLConfigManager - Node will not be marked as historical at shutdown
[Thread-0] 09 Jun 2015 19:01:20,507 INFO AgentKernel - JVM Runtime:
java.home=/usr/java/jdk1.7.0_25/jre
java.vm.vendor=Oracle Corporation
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.runtime.version=1.7.0_25-b15
java.io.tmpdir=/home/apache-tomcat-7.0.42/temp
[Thread-0] 09 Jun 2015 19:01:20,507 INFO AgentKernel - OS Runtime:
os.name=Linux
os.arch=amd64
os.version=2.6.32-504.12.2.el6.x86_64
user.name=michael
user.home=/home/michael
user.dir=/home/apache-tomcat-7.0.42/bin
[Thread-0] 09 Jun 2015 19:01:20,526 INFO AgentKernel - JVM Args : -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager | -XX:PermSize=512m | -XX:MaxPermSize=1024m | -Xms6096m | -Xmx12288m | -javaagent:AppServerAgent-4.0.5.1/javaagent.jar | -Djava.endorsed.dirs=/home/apache-tomcat-7.0.42/endorsed | -Dcatalina.base=/home/apache-tomcat-7.0.42 | -Dcatalina.home=/home/apache-tomcat-7.0.42 | -Djava.io.tmpdir=/home/apache-tomcat-7.0.42/temp |
[Thread-0] 09 Jun 2015 19:01:20,527 INFO AgentKernel - JVM Runtime Name: 22907@ikube.be
[Thread-0] 09 Jun 2015 19:01:20,527 INFO AgentKernel - JVM PID: 22907
[Thread-0] 09 Jun 2015 19:01:20,527 INFO AgentKernel - Running obfuscated agent
[Thread-0] 09 Jun 2015 19:01:20,576 INFO LifeCycleManager - Starting service [DynamicServiceManager]
[Thread-0] 09 Jun 2015 19:01:20,580 INFO DynamicServiceManager - Scheduling DynamicServiceManager at interval of 30 seconds
Try changing the controller config file to say:
<controller-port>443</controller-port>
<controller-ssl-enabled>true</controller-ssl-enabled>
Thanks Bradley, I'll give it a shot, along with the other things mentioned by Arun...
Hi Michael,
If node itself missing in controller UI:
==================
There is disconnect in first post and recent logs, we see details of controller host have two different values which is wrong, above said is evident from below logs snippet:
Thread-0] 09 Jun 2015 19:01:19,943 INFO XMLConfigManager - XML Controller Info Resolver found controller host [paid127.saas.appdynamics.com]
[Thread-0] 09 Jun 2015 19:01:19,944 INFO XMLConfigManager - XML Controller Info Resolver found controller port [443]
[Thread-0] 09 Jun 2015 19:01:19,958 INFO XMLConfigManager - XML Controller Info Resolver found controller host [ikube.be]
[Thread-0] 09 Jun 2015 19:01:19,958 INFO XMLConfigManager - XML Controller Info Resolver found controller port [8181]
[Thread-0] 09 Jun 2015 19:01:19,972 INFO XMLConfigManager - XML Agent Account Info Resolver using account name [IkubeLtd]
[Thread-0] 09 Jun 2015 19:01:19,972 INFO XMLConfigManager - XML Agent Account Info Resolver using account access key [quf23mgu4vn6]
[Thread-0] 09 Jun 2015 19:01:19,975 INFO XMLConfigManager - Configuration Channel is using ControllerInfo:: host:[paid127.saas.appdynamics.com] port:[443] sslEnabled:[true] keystoreFile:[] validation:[UNSPECIFIED]
- If you are using saas controller , Can you provide the details of saas acount in xml elements listed details in controller-info.xml file at path /home/apache-tomcat-7.0.42/bin/AppServerAgent-4.0
controller-host, controller-port, application-name, tier-name, <node-name> <ssl-enabled> set this element to true if 443 https mode to connect to saas UI (if you are not using saas ui, and you are using onPremise local controller host 192.168.1.42 than use 8181 and ssl-enabled set to false,)
also provide values for <account-name> and <account-access-key/> values as well
- restart jvm post saving changes to xml file, Hope that information helps, if issue persists please attach/list latest agent logs content
==================
If node exists in UI but no load, can you confirm the type of request you are making load on Tomcat server, we support Servlet, Struts, JMS, Webservie etc as per settings under Configure -> Instrumentation -> transaction detection screen
Regards,
Arun
Thanks Arun, I'll give it a shot... keep you posted.
Chaps,
So just for completeness and anyone else that might happen upon this post, we are getting no data again. The app looked very interesting from what we saw. But finally we chose NewRelic purely because we could get it to work and AppDynamics not, pity that.
Another day in the life right?...
Have a fantastic day!
Michael
Michael,
Sorry to hear that. When you contacted us before I think that the problem was simply that you had your agents sending their data to the wrong Controller port, which we figured out and cleared up right away. Sorry to hear you had another problem, we would have been glad to help with it (still will be if you're interested). And we're always here in case you want to come back!
Take care,
-Brad