1.2 About This Technical Note

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

• Sun Java System Messaging Server 6.3

• Sun Java System Messaging Server 6 2005Q4

• Sun Java System Messaging Server 6 2005Q1

• Sun Java System Messaging Server 6 2004Q2

• Sun Java System Messaging Server 6 2003Q4

• Sun ONE Messaging Server 6

• iPlanet^TM Messaging Server 5

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 Messaging Sever problems.

If your problem does not conveniently fit into any of the specific categories, supply the general information described in 1.5 What Messaging 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 Messaging Server Debug Data

The prerequisites for collecting debug data for Messaging Server are as follows:

• Make sure you have superuser privileges.

• For the Solaris OS platform, obtain the dbhang and pkg_app scripts from the following location:

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

• 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.

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.

• channel: The channel name where the messages are queued.

• identifier: The Messaging Server instance name used during installation. The installation program automatically added the prefix msg- to the name you specified. For example, if you named the identifier tango, the installation program created msg-tango. This only applies to iPlanet Messaging Server 5.

• messaging-pid: Process ID of a Messaging Server daemon.

• messaging-service-port: Port number used by a Messaging Service (IMAP, POP, HTTP, and so forth).

• msg-instance: The directory on the Messaging Server machine dedicated to holding configuration, maintenance, and information files for a specific instance. This directory is located under server-root. This only applies to iPlanet Messaging Server 5. In Sun Java System Messaging Server 6, it is the config directory.

• server-root: The directory on the Messaging Server machine dedicated to holding the server program, configuration, maintenance, and information files. The default location for the Solaris OS version of Sun Java System Messaging Server 6 is /opt/SUNWmsgsr/. See To Obtain the server-root Variable for more information on determining the value of server-root.

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

To Obtain the server-root Variable

Use the following to obtain the value of the server-root variable.

• Sun Java System Messaging Server (Messaging Server 6):

  Solaris

  pkgparam -v SUNWmsgco

  Linux

  rpm -q --qf '%{INSTALLPREFIX}' sun-messsaging-server

• iPlanet Messaging Server (Messaging Server 5):

  Solaris

  Look in the/etc/msgregistry.inf file.

  Windows

  Look in the C:\windows\system32\etc\msgregistry.inf file.