You can use the stopOgServer script to stop eXtreme Scale server processes.
cd wxs_install_root/bin
Run the stopOgServer script to stop the container server. Use this command only when you are stopping a single container server. If you run the single catalog server stop command on several container servers in succession, you might see performance and churn issues for shard placement.
stopOgServer containerServer -catalogServiceEndPoints MyServer1.company.com:2809
To prevent churn and performance issues for shard placement when you want to stop multiple container servers at the same time, use the following command format. Separate a list of container servers with commas:
stopOgServer containerServer0,containerServer1,containerServer2
-catalogServiceEndPoints MyServer1.company.com:2809
If
you want to stop all of the containers on a specific zone or host,
you can use the -teardown parameter. See Stopping servers gracefully with the xscmd utility for more information.Run the stopOgServer script to stop the catalog server.
stopOgServer.sh catalogServer -catalogServiceEndPoints MyServer1.company.com:2809
Starting a catalog service requires peer access ports and client access ports, if the default ports were not used. Stopping a catalog service requires only the ORB port.
If a container fails to stop, you can enable trace to help with debugging the problem. To enable trace during the stop of a server, add the -traceSpec and -traceFile parameters to the stop commands. The -traceSpec parameter specifies the type of trace to enable and the -traceFile parameter specifies path and name of the file to create and use for the trace data.
cd wxs_install_root/bin
stopOgServer.sh c4 -catalogServiceEndPoints MyServer1.company.com:2809
-traceFile ../logs/c4Trace.log -traceSpec ObjectGrid=all=enabled
After the 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: For more information about stopping embedded servers programmatically, see Using the embedded server API to start and stop servers.