view storage/cli/src/main/resources/com/redhat/thermostat/storage/cli/internal/strings.properties @ 1382:7caa7f9afb14

Separate storage command from agent-cli Backport of PR1608. We get an exception that the RMI registry port is already in use for running "thermostat storage --status". This happens because agent-core's activator creates a thread pool for JMX connections, which in turn creates the RMI registry. My proposed solution is to separate the storage command from the agent bundles, currently it resides in agent-cli. This patch creates a storage-cli bundle that houses StorageCommand and its related classes. There are then some modifications to the ServiceCommand in order to invoke the storage command without having a bundle dependency on storage-cli, which would also entail having to export StorageCommand. Reviewed-by: vanaltj Review-thread: http://icedtea.classpath.org/pipermail/thermostat/2013-December/009022.html PR1648
author Elliott Baron <ebaron@redhat.com>
date Mon, 10 Feb 2014 19:08:50 -0500
parents
children
line wrap: on
line source

COMMAND_STORAGE_ARGUMENT_REQUIRED = either --start or --stop must be given

STORAGE_ALREADY_RUNNING_WITH_PID = Storage is already running with pid {0}
SERVER_SHUTDOWN_COMPLETE = server shutdown complete: {0}
LOG_FILE_AT = log file is here: {0}
CANNOT_START_SERVER = cannot start server {0}, exit status: {1}. Please check that your configuration is valid
CANNOT_SHUTDOWN_SERVER = cannot shutdown server {0}, exit status: {1}. Please check that your configuration is valid
STALE_PID_FILE = stale pid file: {0}
STALE_PID_FILE_NO_MATCHING_PROCESS = A stale pid file ({0}) is present but there is no matching {1} process. Removing stale pid file.
STARTING_STORAGE_SERVER = starting storage server...
CANNOT_EXECUTE_PROCESS = can not execute {0} process. is it installed?
SERVER_LISTENING_ON = server listening on ip: {0}
PID_IS = pid: {0}
MISSING_PROPERTY = {0} property missing
MISSING_PEM = No SSL PEM file specified!
MISSING_PASSPHRASE = No SSL key passphrase set!
MISSING_DB_CONFIG = can't access database configuration file {0}
MISSING_DB_DIR = database directories do not exist...
STORAGE_RUNNING = Storage is running
STORAGE_NOT_RUNNING = Storage is not running