Recommended Data Collection for Crashes and Hangs in Application Server ( Linux )
Complete Application server version
<appserver_install-directory>/bin/asadmin version --verbose
- Tar of the config files
<sjsas-install>/config/asenv.conf
<sjsas-install>/domains/<domain_name>/<instance-config>/*
For 8.x and 9.x
<sjas-install>/nodeagents/<nodeagent_name>/<instance_name>/config/*
Application Server Process Hangs/High CPU
Self-help
- For 9.x
- Please ensure that the worker threads in the domain.xml is tuned. Default is 5.
eg
Change
<request-processing header-buffer-length-in-bytes="8192" initial-thread-count="2" request-timeout-in-seconds="30" thread-count="5" thread-increment="1"/>
to
<request-processing header-buffer-length-in-bytes="8192" initial-thread-count="2" request-timeout-in-seconds="30" thread-count="128" thread-increment="1"/> - Please refer to this Sun blog for more information http://weblogs.java.net/blog/jfarcand/archive/2007/03/configuring_gri_2.html
- Please ensure that the worker threads in the domain.xml is tuned. Default is 5.
Data Collection
- top -bc > top.log or top -bc -p pid > top.log
- ps -L -o pid,tid,pcpu,state -p pid > ps.log [ locate those high readings under the %CPU column ]
Have to perform together with a kill -3 pid. See below command - Time stamp of the issue.
- server.logs that capture the problem occurrences
- Detail the load/number of concurrent users at that time of the problem.
- Does restarting the server resolve the issue?
- After a fresh restart of the server, for how long does it run without problems?
- For 7.x and 8.x
- Issue kill -3 command for 3 times successively with an interval of a minute. This will create the java thread dump in the server.log file.
Please issue kill -3 pid command ONLY during the time of issue.- For 9.x
- Please use the command : asadmin generate-jvm-report --type=thread
- Issue the command a few times over a period of time.
- Please provide us the server.log containing the thread dump.
- For 9.x
- Issue kill -3 command for 3 times successively with an interval of a minute. This will create the java thread dump in the server.log file.
<appserver_install-directory>/domains/<domain_name>/logs/server.log
<appserver_install-directory>/nodeagents/<nodeagent_name>/<instance_name>/logs/server.log
Or <appserver_9.1.x_install-directory>/nodeagents/<nodeagent_name>/<instance_name>/logs/jvm.log
Application Server Process Crash
- Check and sent any core file ( as a result of the application server crash )
- Check for any hs_err_pid.log. By default, the file is created in the working directory of the process
- When was the issue noticed first?(Please provide the exact time stamp of the issue). Does this issue happen during high load or any particular activity? Explain more.
- How often it is occurring?
- Provide the server.log at the time of crash and the access log around the time of the issue
<appserver_install-directory>/domains/<domain_name>/logs/server.log
<appserver_install-directory>/nodeagents/<nodeagent_name>/<instance_name>/logs/server.log
Sign up or Log in to add a comment or watch this page.