2.2 Windows

Recommended Data Collection for Crashes and Hangs in the Application Server ( Windows )

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/*

  • High CPU Application Server Process
    • Launch Process Explorer and locate the application process that indicates high cpu ( java.exe and appserv.exe )

  • Right-click properties
  • locate the tid of the offending process

  • Click on tid ( in this case 3512 ) and click on button "Stack"

  • Copy the content of the stack and paste it into a file
  • Collect the Java Thread Stack dump using the instructions below steps.pdf

Application Server Process Hangs

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

Data Collection

  • Collection of Java Thread Stack Dump ( a few sets of data over a period of time )
    • 7.x and 8.x
      This is a third-party tool : Run the following tool from adaptj - http://www.adaptj.com/main/download
      • Suggested instructions to run Adaptj 's stacktrace : steps.pdf
        Made sure Java option -Xrs is not enabled
    • 9.x
      • Run the command : asadmin generate-jvm-report --type=thread

Application Server Process Crash

  • Check and sent any window dump 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.
  • 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

Labels

kapplicationserver kapplicationserver Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact