stopOgServer script

The stopOgServer script stops servers.

Purpose

By providing its name and catalogServiceEndpoints, you can use the stopOgServer script to stop a server.

Location

The stopOgServer script is in the bin directory of the root directory, for example:
cd objectgridRoot/bin

Usage

To stop a catalog server:

[Windows]
stopOgServer.bat <server> -catalogServiceEndPoints
<csHost:csListenerPort,csHost:csListenerPort> [options]
[Unix]
stopOgServer.sh <server> -catalogServiceEndPoints
<csHost:csListenerPort,csHost:csListenerPort> [options]
To stop an ObjectGrid container server:

[Windows]
stopOgServer.bat <server> -catalogServiceEndPoints
<csHost:csListenerPort,csHost:csListenerPort> [options]
[Unix]
startOgServer.sh -catalogServiceEndPoints
<csHost:csListenerPort,csHost:csListenerPort> [options]

Options

-clientSecurityFile <security properties file>
-traceSpec <trace specification>
Specifies a string that specifies the scope of the trace that is enabled when the server starts.
Example:
  • ObjectGrid=all=enabled
  • ObjectGrid*=all=enabled
-traceFile <trace file>
Specifies the path of a file in which to save trace information.

Example: ../logs/c4Trace.log

-jvmArgs <JVM arguments>
Every parameter after the -jvmArgs option is used to start the server Java™ virtual machine (JVM). When the -jvmArgs option is used, ensure that it is the last optional script argument specified.