1.2 About This Technical Note

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

• Sun Java System Web Proxy Server 3.6 Service Pack 9

• Sun Java System Web Proxy Server 3.6 Service Pack 8

• Sun Java System Web Proxy Server 3.6 Service Pack 7

• Sun Java System Web Proxy Server 3.6 Service Pack 6

• Sun Java System Web Proxy Server 3.6 Service Pack 5

• Sun ONE Web Proxy Server 3.6 Service Pack 4

• Sun ONE Web Proxy Server 3.6 Service Pack 3

• Sun ONE Web Proxy Server 3.6 Service Pack 2

• iPlanet Web Proxy Server 3.6 Service Pack 1

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 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. It provides some troubleshooting, but you should not use this guide as an approach to troubleshooting Web Proxy Server problems.

If your problem does not fit into any of the specific categories, provide the general information described in What Web Proxy Server Debug Data Should You Collect? and clearly explain your problem.

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

1.2.1 Prerequisites for Collecting Web Proxy Server Debug Data

The prerequisites for collecting debug data for Web Proxy Server are as follows:

• Make sure you have superuser privileges.

• For the Solaris platform, obtain the pkg_app script from the following location:

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

• For Windows platform, download the free Debugging Tools for Windows to help in analyzing 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 last version of Debugging Tools and the OS Symbols for your version of Windows. Also, you must add the environment variable NT_SYMBOL_PATH.

  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

The following describes the variables used in the procedures in this document. Gather the values of the variables if you don't already know them 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 slapd-tango, it is the slapd-identifier.

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

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

• proxy-identifier: The Web Proxy Server instance name used during installation. The installation program automatically adds the prefix proxy- to the name you specify. For example, if you name the identifier server1, the installation program creates proxy-server1.

• proxy-instance: The directory on the Web Proxy Server machine dedicated to holding configuration, maintenance, and information files for a specific instance. This directory is located under server-root.

• server-root: The directory on the Web Proxy Server machine dedicated to holding the server program, configuration, maintenance, and information files.

• windbg-root: The directory on the Windows Web Proxy Server machine dedicated to holding the Win Debugger program, and configuration, maintenance, and information files.