Sun ONE logo      Previous      Contents      Index      Next     

Sun ONE Instant Messaging Administrator's Guide

Appendix D  
Troubleshooting Instant Messaging

This chapter lists the common problems that may occur during installation and deployment of Instant Messaging. The log information generated by the various system components on their operation can be extremely useful when trying to isolate or troubleshoot a problem. For details and more information on logging, refer to the section Managing Logging. This section lists the various log files with their default locations on Solaris.

The Multiplexor and Server logs are in the files mux.log and server.log respectively, by default these files are in the directory /var/opt/SUNWiim/default/log. The logging level for Multiplexor and Server log files is controlled in the iim.conf configuration file using the properties iim.log.iim_mux.severity and iim.log.iim_mux.severity. These properties can have the following values:

Logging configuration in portal deployments is determined by the com.iplanet.services.debug.level property. This property can contain the following values:

Table D-1 lists the location of the desktop and archive log files.

Table D-1  The location for the desktop and archive log files

Log File

Default Location

desktop.debug

/var/opt/SUNWam/debug/

IMArchiveSearch.log

/var/opt/SUNWam/debug/

IMArchiveSubmit.log

/var/opt/SUNWam/debug/

Logging information for the Messenger client can be obtained by enabling logging output from the Java Web Start application manager or the Java plug-in manager.

Listed below are some problems and their possible causes and the clues for troubleshooting these problems:

The Messenger client does not load or start

Connection refused and timed out

Authentication errors

IM channel display error

Instant Messaging content is not archived

Server-to-server communication fails to start

The Messenger client does not load or start

The following are the possible causes for this problem:

Where to get the necessary information:

Connection refused and timed out

The following are the possible causes for this problem:

Where to get the necessary information:

Authentication errors

The following are the possible causes for this problem:

Where to get the necessary information:

IM channel display error

The following are the possible causes for this problem:

Where to get the necessary information:

Instant Messaging content is not archived

The following are the possible causes for this problem:

Where to get the necessary information:

Server-to-server communication fails to start

The following are the possible causes for this problem:

Where get the necessary information:

The necessary information can be obtained from the two Instant Messaging server log files.



Previous      Contents      Index      Next     


Copyright 2003 Sun Microsystems, Inc. All rights reserved.