Sun Gathering Debug Data for Sun Java System Application Server

ProcedureTo Collect Debug Data on a Application Server Crashed Process

Use this task to collect data when a Application Server process has stopped (crashed) unexpectedly. Run all the commands on the actual machine where the core file(s) were generated.

  1. Collect the general system information as explained in To Collect Required Debug Data for Any Application Server Problem.

  2. Collect the swap information


    swap -l






    Already provided in C:\report.txt.

  3. Collect the system logs.

    Solaris, Linux





    Go to Start->Settings->Control Panel->Event Viewer->Select Log, and then click Action->Save Log File As and enter a name for the resulting file.

  4. Collect the core files (called “Crash Dumps” in Windows).

    • Solaris

      See 2.2 Configuring Solaris OS to Generate Core Files if a core file was not generated.

    • Linux

      Core dumps are turned off by default in the /etc/profile file. You can make user-specific changes by editing your ~/.bash_profile file. Look for the following line:

      ulimit -S -c 0 > /dev/null 2>&1

      You can either comment out the entire line to set no limit on the size of the core files or set your own maximum size.

    • Windows

      Generate a crash dump during a crash of Application Server by using the following commands:

      Get the appserv process PID:


      Generate a crash dump when the appserv process crashes by executing the following commands:

      C:\windbg-root>adplus.vbs -crash -FullOnFirst -p appserv-pid -o C:\crashdump_dir

      The adplus.vbs command monitors appserv-pid until it crashes and generates the dmp file. Provide the complete generated folder under C:\crashdump_dir.

      Note –

      If you have not installed the Debugging Tools for Windows, you can use the drwtsn32 -i command to select Dr. Watson as the default debugger. Use the drwtsn32 command, check all options, and choose the path for crash dumps. Then provide the dump and the drwtsn32.log files.

  5. (Solaris only) For each core file, provide the output of the following commands.

    cd server-root/bin/https/bin
    file corefile
    pstack corefile
    pmap corefile
    pflags corefile
  6. (Solaris only) Archive the result of the pkg_app script (one core file is sufficient).

    ./pkg_app.ksh application-pid corefile

    Note –

    The Sun Support Center must have the output from the pkg_app script to properly analyze the core file(s). For more information on how to run the pkg_app script, see 2.3.2 Running the pkg_app Script.

    All these commands must be executed on the machine on which the core file(s) are generated.