Java Agent Crashing

[CommunityUser]

Hi,

we have a problem with starting java agent on our server.

Server OS: AIX 6.1 - Technology Level 9 - Service Pack 2

Java Version: 1.6.0

To run java agent we are using command:

java  -javaagent:/tmp/AppServerAgent-ibm/ver4.0.2.0/javaagent.jar

When we run this command we recieve an error (Log1 in attachment).

Server log (from /tmp/AppServerAgent-ibm/ver4.0.2.0/logs/server1/agent.2015_02_27__09_54_26.0.log) in attachment.

controller-info.xml file in attachment

But server appeared in AppDynamics Controller console:

Please, help to resolve this problem.

Thanks.

[Arun_Dasetty]

Hi,

We see two different errors but the main error is the way agent is starting need to be corrected ,

Please find the doc for steps to configure agent -javaagent entry as part of server startup settings

https://docs.appdynamics.com/display/PRO40/Java+Server-Specific+Installation+Settings

if you are planning to monitor particular standaline java applicatin or jar file we request you to start as below:

shell> java  -javaagent:"/tmp/AppServerAgent-ibm/ver4.0.2.0/javaagent.jar"  -jar MyTest.jar 

Where you are trying to run and monitor MyTest.jar (without agent it will look like , shell> java -jar MyTest.jar)

If you still see the issue post configuring server as per docs please send the latest logs , please be sure that javaagent.jar does not have main program and it needs to be part jvm args for monitoring another jar / tomcat as such, Hope that clarifies.

Above said is evident from below java syntax error listed in log provided:
Usage: java [-options] class [args...]

Exception in thread "Thread-2" java.lang.UnsupportedOperationException: cannot get the capability, performing dispose of the retransforming environment

We see few other errors in agent logs but would like to check the behavior post correcting java command arg syntax, Hope that information helps.

Regards,

Arun

[CommunityUser]

Thanks for your reply.
Can you tell me what kind of entry we need to choose for Siebel CRM application.
Thanks.

[Arun_Dasetty]

Hi,

We understood that you do not see OOTB business transaction detection, To better answer your query and to assist you further, we request you to send the following details to provided custom rule conifg to be defined for your app. scenario:

a) We assume that Siebal CRM app is java based application and now you could start it using -javaagent entry fine, Can you please do the following changes and send the requested logs below:

 - Update find-entry-points boolean property to value "true" in controller UI for application agent node associated, refer doc for steps to update node property from UI : https://docs.appdynamics.com/display/PRO40/App+Agent+Node+Properties#AppAgentNodeProperties-editregi...

- restart the JVM after 2-4 minutes after saving node property in UI, send the archive version of <AppServerAgent_dir>/<ver>/logs and conf directory post generate loading on target api:

/tmp/AppServerAgent-ibm/ver4.0.2.0/logs and /tmp/AppServerAgent-ibm/ver4.0.2.0/conf

- We will go through the latest business-transactions-<latest-timestamp>.log and will suggest to define pojo custom rule from api that does calls the business transaction to siebal crm transactions

https://docs.appdynamics.com/display/PRO40/POJO+Entry+Points

Hope that information helps. Keep us posted requested details to assist you further.

[CommunityUser]

Hi,

Thank for your reply.

Logs are in attachment.

[Arun_Dasetty]

Hi,

We could see find-entry-points set to true in logs but could not find any entry points in Business-Transactions.log , Can you please restart JVM and generate load on target API(class/method) that is instantiated in JVM instance for which agent is configured and send the logs for our review to assist you further?

Also let us know runtime period of jvm, we see agent have logs for only 2 minutes, if agent runs for very short period, start with jvm arg listed below and also try to define custom pojo rule under Configure -> Instrumentation -> transaction detection screen in controller UI:

-Dappdynamics.cron.vm=true 

[CommunityUser]

Hi,
Agent have logs for only 2 minutes because it crashes immediately after launch.

[Arun_Dasetty]

Hi,

Can you check the behavior with attached agent archive provided same agent config details or just copy controller-info.xml under <agent-dir>/vers/conf path from old agent directory to new agent_directory/conf path and start agent jvm and see how it goes ?

[CommunityUser]

Hi!
I have just started new agent.
It was started without errors (unlike in the previous), added to controller console, but crashes in two minutes too.
Logs are in attachment.

[Arun_Dasetty]

Hi,

We do not the actual jvm jar/standalone application in log file that you are targettting to monitor, please be sure that agent -javaagent: entry is used part of jvm startup command that is used to monitor another jvm process agent itself will not run as jvm itself, Hope it clarifies

Say: you run java program as below:

cmd> java  -jar myTest.jar

than to start above java program with agent you shoudl run like below:

cmd> java java -javaagent:/tmp/AppServerAgent-3.9.4.0/javaagent.jar -jar myTest.jar

Where user is planning to monitor myTest.jar here, please read my update on Feb 27th once again , we see same error in log provided "Usage: java [-options] class [args...]" .

 Hope it clarifies.

[CommunityUser]

Hi,
we understand that we need run command to monitor specific *.jar file, like:
java -javaagent:/tmp/AppServerAgent-3.9.4.0/javaagent.jar -jar /u01/siebel/siebsrvr/classes/Siebel.jar

But, Siebel CRM consists of more than 200 *.jar files, so we need to run javaagent for each of them?
Can AppDynamics monitor full JVM?
Thanks.

[Arun_Dasetty]

Hi,

Yes one -javaagent agent node-name entry will monitor one jvm instance for which it is configured with. Can you add the -javaagent entry as part of jvm startup of Siebal application which loads the jvm classes for all 200 hars

If you are starting Siebal as below  to start Siebal application:

java -jar /u01/siebel/siebsrvr/classes/Siebel.jar

than we confirm yes, you should use as you stated:

java -javaagent:/tmp/AppServerAgent-3.9.4.0/javaagent.jar -jar /u01/siebel/siebsrvr/classes/Siebel.jar

Make either agent directory is different or node-name is left blank in controller-info.xml  and provided -Dappdynamics.agent.nodeName arg with unique node name value if you want to monitor multiple jars/jvm instances, Hope that infromation helps.