1.2 About This Technical Note

This document covers the following versions of Sun Java System Web Server on the Solaris^TM, HP-UX, Linux, and Microsoft Windows platforms:

• Sun Java System Web Server 7.0

• Sun Java System Web Server 6.1 (SunONE Web Server)

• iPlanet^TM Web Server 6.0

The versions mentioned above include all update release or service packs for the products.

You can use this document in all types of environments, including test, pre-production, and production. Verbose debugging is not used (to reduce performance impact), except when it is deemed necessary. At the same time, it is possible that the problem could disappear when you configure logging for debug mode. However, this is the minimum requirement to understand the problem. In the majority of cases, the debug data described in this document is sufficient to analyze the problem.

This document does not provide workarounds, techniques or tools to analyze debug data.

If your problem does not fit into any of the specific categories, provide the general information described in 1.5 Types of Web Server Debug Data and clearly explain your problem.

If the information you initially provide is not sufficient to find the root cause of the problem, Sun Support Center will ask for more details, as needed.

1.2.1 Prerequisites for Gathering Web Server Debug Data

The prerequisites for Sun GDD for Web Server are as follows:

• Make sure you have superuser privileges.

• For the Solaris platform, obtain the pkg_app and the wshang scripts and for UNIX and Linux, obtain the webinfo scripts from the following location:

  http://www.sun.com/bigadmin/scripts/indexSjs.html

• For Windows platform, download the free Debugging Tools for Windows to analyze the process hang problems.

  ---

  Note –

  The debugger Dr. Watson is not useful for process hang problems because it cannot generate a crash dump on a running process.

  ---

  Download the free Debugging Tools from the following location:

  http://www.microsoft.com/whdc/devtools/debugging/default.mspx

  Install the latest version of Debugging Tools and the OS Symbols for your version of Windows. Also, you must add the environment variable NT_SYMBOL_PATH in the windows environment variable. Refer to Operating System version documentation or follow the installation guide for the OS Symbols package.

  Use the command drwtsn32 -i to select Dr. Watson as the default debugger. Use the command drwtsn32, check all options, and choose the path for crash dumps.

1.2.2 Variables Used in This Technical Note

This section describes the variables used in the procedures in this document. Gather the values of the variables before you try to do the procedures.

• slapd-identifier: The Directory Server instance name used during installation. The installation program automatically added the prefix slapd- to the name you specified. For example, if you named the identifier tango, the installation program created is slapd-tango and slapd-tango is the slapd-identifier.

• web-pid: Process ID of a Web Server daemon.

• web-port: Port number on which the Web Server is listening.

• web-identifier: The Web Server instance name used during installation. The installation program automatically adds the prefix https- to the name you specified. For example, if you named the identifier tango, the installation program created https-tango, it is the web-identifier.

• server-root: The directory on the Web Server machine that stores the server specific information. This directory holds the server program, configuration, maintenance, and log files.

• windbg-root: The directory on the Windows Web Server machine that stores the Win Debugger program, and configuration, maintenance, and information files.