Glassfish 2.2 on SLES 10 SP2 No connection

[CommunityUser]

Hi

I'm having problem connecting the JAVA agent to our central server Windwo 2012 running the PRO edition. Pro is running on Win 2012 server, Glassfish (Sun JVM 1.6) is running  SLES 10 SP2.  Agent installs/starts apparently fine, no firewalls between the servers etc but AppDynamics doesn't pick anything up....

Cheers

[Arun_Dasetty]

Hi,

Can you please provide the following to assist you better:

- zipped version of agent logs directory under <agent_dir>/logs

- glassfish domian server.log and startup console log

- screenshots from controller UI depiciting the issue for no load discovered

Thanks,

Arun

[CommunityUser]

Hi Arun

JVM setting setting from the Glassfish GUI

-javaagent:/opt/sun/glassfish/agent/javaagent.jar=uniqueID=mdcglass12r

Startup from the cli

mdcglass12r:/opt/sun/glassfish/domains/domain1/config # /etc/init.d/glassfish start
Starting Domain domain1, please wait.
Log redirected to /opt/sun/glassfish/domains/domain1/logs/server.log.
Redirecting output to /opt/sun/glassfish/domains/domain1/logs/server.log
Install Directory resolved to[/opt/sun/glassfish/agent]
[INFO]: JavaAgent - Using Java Agent Version [Server Agent v3.7.11.1 GA #2013-10-23_17-07-44 r41149afdb8ce39025051c25382b1cf77e2a7fed0 21]
[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 [mdcglass12r]
[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using node name [mdcglass12r]
[INFO]: AgentInstallManager - Full Agent Registration Info Resolver finished running
[INFO]: AgentInstallManager - Agent runtime directory set to [/opt/sun/glassfish/agent]
[INFO]: AgentInstallManager - Agent node directory set to [mdcglass12r]
[INFO]: JavaAgent - Java Agent Directory [/opt/sun/glassfish/agent]
Agent Logging Directory [/opt/sun/glassfish/agent/logs/mdcglass12r]
Running obfuscated agent
Started AppDynamics Java Agent Successfully.
Domain domain1 is ready to receive client requests. Additional services are being started in background.
Domain [domain1] is running [Sun Java System Application Server 9.1_02 (build b04-fcs)] with its configuration and logs at: [/opt/sun/glassfish/domains].
Admin Console is available at [http://localhost:4848].
Use the same port [4848] for "asadmin" commands.
User web applications are available at these URLs:
[http://localhost:80 http://localhost:81 ].
Following web-contexts are available:
[/web1 /__wstx-services ].
Standard JMX Clients (like JConsole) can connect to JMXServiceURL:
[service:jmx:rmi:///jndi/rmi://mdcglass12r:8686/jmxrmi] for domain management purposes.
Domain listens on at least following ports for connections:
[80 4848 81 3700 3820 3920 8686 ].
Domain does not support application server clusters and other standalone instances.

mdcglass12r:/opt/sun/glassfish/domains/domain1/config #

Agent Log file attached

Glassfish Log file attached

Lots of errors in both log files..

Many thanks

[Arun_Dasetty]

Hi,

We see the following errors in agent.logs, from which it is evident that controller UI is not up at the same machine in whcih you are trying to start glassfish with -javaagent configured:

==================================

[Thread-0] 11 Nov 2013 10:01:37,968  INFO XMLConfigManager - Default IP Address Resolver found IP addresses [[fe80:0:0:0:250:56ff:fe8f:3b4c%2, 151.129.137.41]]
[Thread-0] 11 Nov 2013 10:01:37,981  INFO XMLConfigManager - XML Controller Info Resolver found valid config [Controller Host: localhost; Controller Port: 8090; ssl-enabled: false]
[Thread-0] 11 Nov 2013 10:01:38,941  WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [localhost], port[8090], exception [Fatal transport error: Connection refused]
[Thread-0] 11 Nov 2013 10:01:38,946  WARN AgentErrorProcessor - Agent error occurred, [name,transformId]=[com.singularity.CONFIG.ConfigurationChannel - java.net.ConnectException,2147483647]
[Thread-0] 11 Nov 2013 10:01:38,946  WARN AgentErrorProcessor - 4 instance(s) remaining before error log is silenced
[Thread-0] 11 Nov 2013 10:01:38,947 ERROR ConfigurationChannel - Exception: Connection refused
java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(Native Method)

==================================

We understood that glassfish with agent is running at IP 151.129.137.41  or the same machine in which contorller is installed, if this is the case, please make sure that controller UI is up and accessible at browser at http://localhost:8090/controller Or http://151.129.137.41:8090/controller, we request to check this as we see connection errors in agent logs from which it is clear controller on same localhost machine is not up and running.
 

Thanks,

Arun

[CommunityUser]

Hi Arun

"We see the following errors in agent.logs, from which it is evident that controller UI is not up at the same machine in whcih you are trying to start glassfish with -javaagent configured:"

You are correct, it was my understanding that you could run the controller on a seperate server, and all the JVM agents feed into that server.  Is this not the case?

Thanks

[Arun_Dasetty]

Hi,

We see that we provide saas controller at aws if you have saas account, and if you do not have saas account http://<account-name>.saas.appdynamics.com:80/controller

If you not have requested for saas account then you must install controller on your test machne and that machine instance should be accessible from agent machine

we request you to go through the following docs for more details:

For on premise/local controller:
http://docs.appdynamics.com/display/PRO13S/Install+the+Controller

For saas controller:

http://docs.appdynamics.com/display/PRO13S/Get+Started+with+AppDynamics+SaaS

Thanks,

Arun

[CommunityUser]

Hi,

To add to Arun's point I am guessing that you may have not configured the agent to point to the Controller (whether SaaS or on-premise).  Go to <agent_home>/conf/controller-info.xml on your Glassfish server to configure the following:

 - Controller host

 - Controller port

 - Controller SSL enabled

 - Account name and account key (SaaS only)

With this the agent should register with your Controller but check the agent logs to see whether there are any issues with connecting due to other issues such as firewalls.

Steve