The connector command is used for various operations that affect the Tungsten Connector, for example, starting and stopping the Tungsten Connector, getting status, updating and debugging.
When using the connector command-line tool, the following sub-commands are available:
Table 7.2. Connector Command Line Sub-Commands
| Option | Description |
|---|---|
client-list | Return a list of the current client connections through this connector. |
cluster-status | Return the cluster status, as the connector currently understands it. This is the command-line alternative to the inline cluster status command. |
condrestart | Restart only if already running |
console | Launch in the current console (instead of a daemon) |
dump | Request a Java thread dump (if connector is running) |
drain {seconds} | An alias for graceful-stop. Specifying no value for {seconds} will wait indefinitely. |
graceful-stop {seconds} | Stops the connector gracefully, allowing outstanding open connections to finish and close before the connector process is stopped. {seconds} is an integer of zero or more, and is required. The connector will shut down immediately if there are no active connections. Specifying zero (0) wlll cause a shutdown without waiting for connections to terminate. |
install | Install the service to automatically start when the system boots |
reconfigure | Reconfigure the connector by forcing the connector to reread the configuration, including the configuration files and user.map. |
remove | Remove the service from starting during boot |
restart | Stop connector if already running and then start |
start | Start in the background as a daemon process |
status | Query the current status |
stop | Stop if running (whether as a daemon or in another console) Optional timeout in seconds can be provided (From release 6.1.19 only) |
For more information, please see Section 9.9, “The connector Command”.