See the WebSphere eXtreme Scale Wiki for links to eXtreme Scale Version 7.0 documentation.
If you log in
with your developerWorks ID, you can leave comments and feedback for the development team.
ObjectGrid servers produce regular logs and can optionally produce trace logs.
Logs
Logs are in different locations depending on whether ObjectGrid is running in WebSphere Extended Deployment or alone.
Logs with ObjectGrid in WebSphere Extended Deployment
Logs and trace are in the same location where the server is configured to send logs. See the WebSphere Network Deployment information center for more information on Working with logs.
Logs with ObjectGrid stand-alone
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 the server command was launched.
Setting log location for container servers
By default, the logs for a container are where the server command was launched. 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 for the logs and optional trace file. ObjectGrid 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 using the traceSpec option.
To use a properties file during container startup, use the -serverProps option and provide the server properties file location. See Starting ObjectGrid server processes and Starting command line parameters for more information.
Common information messages to look for in the SystemOut.log file are start confirmation messages. These messages include Open for business and Entering peer mode.
Using trace
You might need to trace a server if a problem occurs and IBM support requests trace to track the problem. IBM support provides the trace specification to use.
Setting trace with WebSphere Extended Deployment
See the WebSphere Network Deployment information center for information on working with trace.
Setting trace on a stand-alone catalog server
Set trace on a catalog server by using the -traceSpec and -\traceFile parameters during catalog server startup. For example:
startOgServer.sh catalogServer -traceSpec ObjectGridPlacement=all=enabled -traceFile /home/user1/logs/trace.log
See Starting a catalog service for more details on starting a catalog service.
Setting trace on a stand-alone container server
You can enable trace on a container process in two ways. Either create a server properties file as explained in the logs section, or enable trace by using the command line on startup.
To enable container trace with a server properties file, update the traceSpac property with the required trace specification.
To enable container trace using start parameters, use the -traceSpec and -\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
See Starting ObjectGrid server processes for more details on starting a container process.
Setting trace with ObjectGridManager
Another option is to set trace during runtime on an ObjectGridManager. Setting trace on an ObjectGridManager can be used to get trace on an ObjectGrid client while it connects to an ObjectGrid and commits transactions. To set trace on an ObjectGridManager, 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");
All trace options
For all of trace specification options see Trace options.
The 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 appear 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
Messages
For more details about specific messags that appear in the logs, see ObjectGrid Messages.
© Copyright IBM Corporation 2007,2009. All Rights Reserved.
