Using JVM logs to troubleshoot a Sametime server
To start troubleshooting a problem, check the JVM log files first. These log files collect output for the SystemOut.log and SystemErr.log output streams for the application server process.
About this task
An application can write print data to the JVM logs either directly in the form of
System.out.print()
or System.err.print()
method calls or by
calling a JVM function, such as Exception.printStackTrace()
. In addition, the
SystemOut.log JVM log contains system message events written by the WebSphere® Application Server. In the case of a WebSphere Application Server Network Deployment
configuration, JVM logs are also created for the deployment manager and each node manager, since
they also represent JVMs.- SystemOut.log is more useful monitoring the health of the running application server but can help in determining a problem, although it's better to use the IBM® Service log and the advanced capabilities of the Log Analyzer to determine a problem.
- SystemErr.log contains exception stack trace information that is useful when performing problem analysis.
The JVM log files are self-managing to the extent that you can configure the log file size and how many historical, or archived, files to keep. For information on setting log file size, see Setting log file size and rotation.
You can use JVM log files to troubleshoot the
following Sametime® servers:
- SIP Proxy/Registrar
- Conference Manager
- Video Manager
- Meeting Server
- Advanced Server
- Bandwidth Manager
- Gateway Server