Administration guide > Troubleshoot


Enable trace


Trace within a WAS environment

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 -traceSpec and -traceFile during catalog service startup...

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

If you start the catalog service in...

<eXtremeScale_home>/bin

...the logs and trace files will be in...

<eXtremeScale_home>/bin/logs/<catalog_service_name>


Trace on a stand-alone container

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 -traceSpec and -traceFile...

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

<eXtremeScale_home>/bin

...the logs and trace files are in...

<eXtremeScale_home>/bin/logs/<server_name>


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 Monitor with the xsAdmin sample utility for more information.


ffdc directories 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


Parent topic:

Troubleshoot


Related tasks

Enable logs
Troubleshoot installation
Troubleshoot client connectivity
Troubleshoot loaders
Troubleshoot XML configuration
Troubleshoot security

Related reference

Trace options
IBM Support Assistant for WebSphere eXtreme Scale
Messages
Release notes