This document covers the following versions of Sun Java System Portal Server on the SolarisTM Operating System, HP-UX, Linux, and Microsoft Windows platforms:
Sun Java System Portal Server 6 2005Q4
Sun Java System Portal Server 6 2005Q1
Sun Java System Portal Server 6 2004Q2
Sun Java System Portal Server 6 2003Q4
Sun ONE Portal Server 6.0
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 nor techniques or tools to analyze debug data. It provides some troubleshooting, but you should not use this guide as an approach to troubleshooting Portal Sever problems.
If your problem does not conveniently fit into any of the specific categories, supply the general information described in 1.5 What Portal 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.
The prerequisites for collecting debug data for Portal Server are as follows:
Make sure you have superuser privileges.
For the Solaris OS platform, obtain the ps6info.sh and pkg_app scripts from the following location:
On the Windows platform, download the free Debugging Tools for Windows to help in analyzing process hang problems. 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.
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.
instance-dir: The directory on the Portal 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 Portal Server machine dedicated to holding the server program, configuration, maintenance, and information files.
web-pid: Process ID of the Web Server daemon.