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.
Use the stopOgServer.sh script on Unix platforms or stopOgServer.bat on Windows platforms to stop ObjectGrid server processes.
ObjectGrid Container Processes
This section focuses on stopping ObjectGrid containers. Once an ObjectGrid container process has been started, you can stop that process with stopOgServer.sh or stopOgServer.bat scripts.
To stop a container, type the following commands from the command-line:
- cd objectgridRoot/bin
- stopOgServer.sh c0 -catalogServiceEndpoints MyServer1.company.com:2809
 | Warning
On the container, the -catalogServiceEndpoints option is used to reference the Object Request Broker (ORB) host and port on the catalog service. The catalog service uses -listenerHost and -listenerPort to specify the host and port for ORB binding or accepts the default binding. When stopping a container, use -catalogServiceEndpoints to reference the values passed to -listenerHost and -listenerPort on the catalog service. If -listenerHost and -listenerPort are not used when starting the catalog service, the ORB binds to port 2809 on the catalog service's localhost.
The -catalogServiceEndpoints option should NOT be used to reference the hosts and ports that were passed to the -catalogServiceEndpoints on the catalog service. On the catalog service, the -catalogServiceEndpoints option is used to specify ports necessary for static server configuration. |
This process is identified by c0, the first argument passed to the script. For this example, assume that a single catalog service is running on port 2809 on MyServer1.company.com.
Catalog Service Processes
To stop a catalog service process, type the following commands from the command-line:
- cd objectgridRoot/bin
- stopOgServer.sh catalogServer -bootstrap MyServer1.company.com:6601
This process is identified by catalogServer, the first argument passed to the script. For this example, assume that the catalog service was started on MyServer1.company.com with clientAccessPort 6601.
Enabling trace at startup
If a container fails to stop, trace can be useful in debugging the problem. To enable trace during the stop of a server, add the -traceSpec and -traceFile parameters to the stop commands. The -traceSpec is the type of trace to enable and the -traceFile is path and name of the traceFile to create and use.
Issue the following commands to enable stop trace on c4:
- cd objectgridRoot/bin
- stopOgServer.sh c4 -catalogServiceEndpoints MyServer1.company.com:2809 -traceFile ../logs/c4Trace.log -traceSpec ObjectGrid=all=enabled
Once trace is obtained, look for errors related to port conflicts, missing classes, missing or incorrect XML files or any stack traces.
Suggested startup trace specifications are:
ObjectGrid=all=enabled
ObjectGrid*=all=enabled
For all of the trace specification options, see Trace options
Command line parameters
For all of the command line options for stopping servers, see Stopping command line parameters.
© Copyright IBM Corporation 2007,2009. All Rights Reserved.
