WebSphere eXtreme Scale Administration Guide > Troubleshoot

Logs and trace

You can use logs and trace to monitor and troubleshoot your environment. Logs are in different locations depending on your configuration. You might need to provide trace for a server when you work with IBM support.

Logs with WebSphere Application Server

See the WebSphere Application Server Information Center for more information.

Logs with WebSphere eXtreme Scale in a stand-alone environment

With stand-alone catalog and container servers, you set the location of logs and any trace specification. The catalog server logs are in the location where you ran the start server command.

Set the log location for container servers

By default, the logs for a container are in the directory where the server command was run. If you start the servers in the <eXtremeScale_home>/bin directory, the logs and trace files are in the logs/<server_name> directories in the bin directory.

To specify an alternate location of a container server logs, create a properties file, such as a server.properties file, with the following contents:

workingDirectory=<directory> 
traceSpec= 
systemStreamToFileEnabled=true

The workingDirectory property is the root directory for the logs and optional trace file. WebSphere eXtreme Scale creates a directory with the name of the container server with a SystemOut.log file, a SystemErr.log file, and a trace file if trace was enabled with the traceSpec option. To use a properties file during container startup, use the -serverProps option and provide the server properties file location.

SeeStart stand-alone WebSphere eXtreme Scale servers and startOgServer script for more information.

Common information messages to look for in the SystemOut.log file are start confirmation messages. For more information about a specific message, see Messages.

Trace with WebSphere Application Server

See the WebSphere Application Server Information Center for more information.

Trace on the catalog service

You can set trace on a catalog service by using the -traceSpec and -traceFile parameters during catalog service startup. For example:

startOgServer.sh catalogServer -traceSpec 
ObjectGridPlacement=all=enabled -traceFile 
/home/user1/logs/trace.log

If you start the catalog service in the <eXtremeScale_home>/bin directory, the logs and trace files will be in a logs/<catalog_service_name> directory in the bin directory. See Start a stand-alone catalog service for more details on starting a catalog service.

Trace on a stand-alone container server

You can enable trace on a container server in two ways. You can create a server properties file as explained in the logs section, or you can enable trace by using the command line on startup. To enable container trace with a server properties file, update the traceSpec property with the required trace specification. To enable container trace using start parameters, use the -traceSpecand -traceFile parameters. For example:

startOgServer.sh c0 -objectGridFile ../xml/myObjectGrid.xml 
-deploymentPolicyFile ../xml/myDepPolicy.xml -catalogServiceEndpoints 
server1.rchland.ibm.com:2809 -traceSpec 
ObjectGridPlacement=all=enabled -traceFile /home/user1/logs/trace.log

If you start the server in the <eXtremeScale_home>/bin directory, the logs and trace files are in the logs/<server_name> directories in the bin directory See Start container processes for more details on starting a container process.

Trace with the ObjectGridManager interface

Another option is to set trace during run time on an ObjectGridManager interface. Setting trace on an ObjectGridManager interface can be used to get trace on an eXtreme Scale client while it connects to an eXtreme Scale and commits transactions.

To set trace on an ObjectGridManager interface, supply a trace specification and a trace log.

ObjectGridManager manager = ObjectGridManagerFactory.getObjectGridManager();
...
manager.setTraceEnabled(true);
manager.setTraceFileName("logs/myClient.log");
manager.setTraceSpecification("ObjectGridReplication=all=enabled");

Enable trace with the xsadmin utility

To enable trace with the xsadmin utility, use the setTraceSpec option. Use the xsadmin utility to enable trace on a stand-alone environment during run time instead of during startup. You can enable trace on all servers and catalog services or you can filter the servers based on the ObjectGrid name, and so on. For example, to enable ObjectGridReplication trace with access to the catalog service server, run:

<eXtremeScale_home>/bin>xsadmin.bat -setTraceSpec "ObjectGridReplication=all=enabled"

You can also disable trace by setting the trace specification to *=all=disabled. See Use the xsAdmin sample utility for more information.

ffdc directory and files

FFDC files are for IBM support to aid in debug. These files might be requested by IBM support if a problem occurs.

These files are in a directory labeled, ffdc, and contain files that resemble the following:

server2_exception.log
server2_20802080_07.03.05_10.52.18_0.txt

• Trace options
  You can enable trace to provide information about your environment to IBM support.

Parent topic

Monitor the deployment environment

Parent topic

Troubleshoot

Related concepts

Start and stop secure eXtreme Scale servers

Related tasks

Start stand-alone WebSphere eXtreme Scale servers

Start a stand-alone catalog service

Start container processes

+

Search Tips   |   Advanced Search