用Java Service Wrapper 注册一个系统服务

为什么80%的码农都做不了架构师？>>>   

之前要想在系统开机启动一个Java进程，一般都是用脚本写到rc.local中。

还有一种办法是写了个服务脚本把它注册到系统服务，也可以开机启动。并可以通过service命令进行管理。

JavaServiceWrapper就是帮我们来做这个事。

下载地址在这里：

http://wrapper.tanukisoftware.com/doc/english/download.jsp

有三个版本，社区版本是免费的。其他要钱也更高级，可以管理服务进程的一些异常情况。对于注册服务来说，社区版本也够用了。
 

我的原进程就是一个单一个jar包，把所有的依赖都打到一起了。通过下面的脚本启动：

java -jar xxx.jar

这个wrapper怎么用呢。下面就以linux版本做一个例子。

文件复制

下载linux对应版本后解压，从里面找到以下几个文件放到我的程序目录下：

wrapper
wrapper.conf
libwrapper.so
wrapper.jar
demoapp

修改wrapper.conf 

这个是wrapper在启动服务时的一些配置，主要改动如下，其他详细配置可看官方文档。

wrapper.lang.encoding=UTF-8
wrapper.java.command=/usr/local/jdk1.8.0_60/bin/java

wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperJarApp
wrapper.java.classpath.1=./wrapper.jar
wrapper.java.classpath.2=/usr/local/jdk1.8.0_60/lib/dt.jar
wrapper.java.classpath.3=/usr/local/jdk1.8.0_60/lib/tools.jar
wrapper.java.classpath.4=./xxx.jar
wrapper.java.classpath.5=./log4j2.xml
wrapper.java.classpath.6=META-INF/MANIFEST.MF
wrapper.java.library.path.1=./
wrapper.app.parameter.1=./xxx.jar
wrapper.console.title=@app.long.name@

wrapper.name=@app.name@
wrapper.displayname=@app.long.name@
wrapper.description=@app.description@

修改demoapp

改为当前程序要注册的服务的信息

# Application
APP_NAME="xxx-service"
APP_LONG_NAME="xxx service"

# Wrapper
WRAPPER_CMD="./wrapper"
WRAPPER_CONF="./wrapper.conf"

执行demoapp install

将服务注册到系统

demoapp install

再启动一下系统就OK了

通过jps -lm可以看到启动的进程信息

1464 org.tanukisoftware.wrapper.WrapperJarApp ./xxx.jar

ps -ef | grep java 一下能看到启动了两个进程，有一个是wrapper。

netstat -ntap 还能看到这两个进程之间有一个内部通信连接。

再用service xxx-service status看一下服务状态, xxx-service 是在demoapp脚本里写的名称

xxx service is running: PID:1462, Wrapper:STARTED, Java:STARTED

 

附配置文件详解

Properties added after the initial release are followed by the Wrapper version in which they were implemented.

[A]

• wrapper.adviser (3.1.0)

  The Wrapper contains an adviser which will output advice whenever certain common problems are detected.

• wrapper.anchorfile (3.1.1)

  Causes the Wrapper to create an anchor file on startup.

• wrapper.anchorfile.poll_interval (3.1.1)

  Controls monitoring intervals testing the existence of the anchor file.

• wrapper.anchorfile.umask (3.2.0)

  Specifies the umask to use when creating the anchor file

• wrapper.app.parameter.<n> (1.0.0)

  Configuration of parameters when applications are launched.

• wrapper.app.parameter_file (3.5.17)

  Specifies the parameters to be used by the JVM.

• wrapper.app.parameter_file.stripquotes (3.5.17)

  Configures a solution using parameters with stripquotes.

[B]

• wrapper.backend.type (3.5.8)

  Configures the communication between the Wrapper's process and the class running within the JVM.

[C]

• wrapper.check.deadlock (3.5.0) (Std/Pro)

  Configures the detection of deadlocks.

• wrapper.check.deadlock.action (3.5.0) (Std/Pro)

  Configuration of actions to take place when deadlocks are detected.

• wrapper.check.deadlock.interval (3.5.0) (Std/Pro)

  Configuration of intervals detecting deadlocks.

• wrapper.check.deadlock.output (3.5.0) (Std/Pro)

  Configuration of values generated and registered after deadlocks are detected.

• wrapper.child.status.loglevel (3.4.0) (Pro)

  Configures the launching and administration of child processes.

• wrapper.commandfile (3.2.0)

  Configuration of commands to be executed.

• wrapper.commandfile.enable_tests (3.5.0)

  Configuration used for testing purposes.

• wrapper.commandfile.poll_interval (3.2.0)

  Controls regular intervals used to test the existence of command files.

• wrapper.console.direct (3.5.21)

  The Wrapper will make use of Windows APIs to write console log output to the console window.

• wrapper.console.error_to_stderr (3.5.3)

  Controls whether levels of log output in the console are logged to stdout or stderr.

• wrapper.console.fatal_to_stderr (3.5.3)

  Controls whether levels of log output in the console are logged to stdout or stderr.

• wrapper.console.flush (3.2.0)

  Configures the Wrapper to implicitly flush stdout after each line of output is sent to the console.

• wrapper.console.format (1.0.0)

  Configures the format of the output sent to the console using tokens.

• wrapper.console.loglevel (1.0.0)

  Configures different log levels for the output sent to the console.

• wrapper.console.title (3.1.0)

  Configures the Title Bar of the console in which the Wrapper is running.

• wrapper.console.title.<platform> (3.3.0)

  Configures the title based on the platform by appending the platform name to the property.

• wrapper.console.warn_to_stderr (3.5.3)

  Controls whether levels of log output in the console are logged to stdout or stderr.

• wrapper.cpu_affinity.set (3.5.27) (Pro)

  Defines whether the processor affinity feature is enabled for the Java Service Wrapper.

• wrapper.cpu_affinity.default (3.5.27) (Pro)

  Enables or disables by default all CPUs of the machine for the Java Service Wrapper.

• wrapper.cpu_affinity.<n> (3.5.27) (Pro)

  Overrides wrapper.cpu_affinity.default and enables or disables a specific CPU for the Java Service Wrapper.

• wrapper.cpu_affinity.strict (3.5.27) (Pro)

  Defines if the wrapper should stop when its CPU affinity configuration causes an exception.

• wrapper.cpu.timeout (2.2.8)

  Configures the number of seconds without CPU before the JVM sends a warning and extend timeouts.

[D]

• wrapper.daemonize (3.0.0)

  Spawns a fork of the Wrapper process as a detached non-session group leader.

• wrapper.debug (1.0.0)

  Enables debug logging both to the console and log file.

• wrapper.description (3.3.0)

  Configures the Service Description to use in error messages, events, etc.

• wrapper.disable_console_input (3.3.2)

  Disables the Wrapper's ability to process console input in the JVM.

• wrapper.disable_forced_shutdown (3.5.15)

  Configures different values to disable forced shutdowns in a Windows console or UNIX shell.

• wrapper.disable_restarts (3.2.0)

  Disables all JVM restarting by the Wrapper, including restarts caused by errors and requested restarts from within the JVM.

• wrapper.disable_restarts.automatic (3.3.4)

  Disables automatic JVM restarting by the Wrapper, including restarts when the JVM crashes or exits unexpectedly.

• wrapper.disable_shutdown_hook (1.0.0)

  Disables detection of calls to System.exit()

• wrapper.disable_test (3.5.16)

  The Wrapper Manager contains several methods used for testing the Wrapper's failure modes, which can also be disabled.

• wrapper.displayname (3.3.0)

  Configures the display name of the service used in error messages, events, etc.

[E]

• wrapper.environment.dump (3.5.0)

  Configures the Wrapper to dump all of the environment variables visible to the Wrapper.

• wrapper.event.<event_name>.command.argv.<n> (3.3.0) (Pro)

  Used to specify the arguments of a command executed in response to a specific event.

• wrapper.event.<event_name>.command.block (3.4.1) (Pro)

  Tells the Wrapper whether or not to wait for the command to complete before allowing the Wrapper to continue.

• wrapper.event.<event_name>.command.block.action (3.4.1) (Pro)

  Configures how the Wrapper behaves when a configured Event Command fails to complete within the specified timeout.

• wrapper.event.<event_name>.command.block.timeout (3.3.0) (Pro)

  Configures how long the Wrapper will wait for a configured event to complete.

• wrapper.event.<event_name>.command.loglevel (3.3.0) (Pro)

  Configures different log levels, which are used to tell the Wrapper how to log information about event commands being executed.

• wrapper.event.<event_name>.command.on_exit.<n> (3.3.0) (Pro)

  Controls what the Wrapper will do in response to specific exit codes of event commands.

• wrapper.event.<event_name>.email (3.3.0) (Pro)

  Configures whether or not emails should be sent for a particular event.

• wrapper.event.<event_name>.email.attach_log (3.4.0) (Pro)

  Enables sending a log file in the attachments of the Notification emails sent by the Wrapper.

  • wrapper.event.default.email.lines (3.4.0) (Pro)

    Specifies the number of lines the log file sent in the attachments.

  • wrapper.event.default.email.maillog.format (3.4.0) (Pro)

    Defines the format of the log file in the attachments.

  • wrapper.event.default.email.maillog.loglevel (3.4.0) (Pro)

    Specifies the loglevel of the log file in the attachments.

• wrapper.event.<event_name>.email.body (3.3.0) (Pro)

  Configures the body of alert emails.

• wrapper.event.<event_name>.email.client.host (3.3.2) (Pro)
• wrapper.event.<event_name>.email.debug (3.3.0) (Pro)
• wrapper.event.<event_name>.email.sender (3.3.0) (Pro)
• wrapper.event.<event_name>.email.receive.timeout (3.3.2) (Pro)
• wrapper.event.<event_name>.email.send.timeout (3.3.2) (Pro)
• wrapper.event.<event_name>.email.smtp.auth.userid (3.5.3) (Pro)

  Specifies the user Id to use for authentication when connecting to a SMTP server to send an email.

• wrapper.event.<event_name>.email.smtp.auth.type (3.5.3) (Pro)

  Specifies an authentication method to use when connecting to an SMTP server to send an email.

• wrapper.event.<event_name>.email.smtp.auth.password (3.5.3) (Pro)

  Specifies the password to use for authentication when connecting to an SMTP server to send an email.

• wrapper.event.<event_name>.email.smtp.host (3.3.0) (Pro)

  Configures the SMTP host which the Wrapper will attempt to connect to when sending emails.

• wrapper.event.<event_name>.email.smtp.port (3.3.0) (Pro)

  Configures the SMTP port which the Wrapper will attempt to connect to when sending emails.

• wrapper.event.<event_name>.email.subject (3.3.0) (Pro)

  Customizes the subject of emails sent for all emails ('default') or for emails sent in response to individual events.

• wrapper.event.<event_name>.email.recipient (3.3.0) (Pro)

  Specifies the email(s) to send the alert mail to.

• wrapper.event.<event_name>.loglevel (3.3.6) (Pro)

  Controls the log level at which a message will be logged each time a specific event takes place.

• wrapper.event.<event_name>.message (3.3.6) (Pro)

  Controls the message which will be logged each time a specific event takes place.

• wrapper.event.<event_name>.set_environment (3.3.0 (Deprecated as of 3.3.6)) (Pro)

[F]

• wrapper.filter.action.<n> (3.0.0)

  Configures filters firing useful actions to monitor your Java applications.

• wrapper.filter.allow_wildcards.<n> (3.5.5)

  Tells the Wrapper to process any wildcards to match a specified filter.

• wrapper.filter.message.<n> (3.5.0)

  Controls messages displayed to users when a trigger is fired.

• wrapper.filter.trigger.<n> (3.0.0)

  Configures triggers which can be any string.

[I]

• wrapper.ignore_sequence_gaps (3.3.6)

  Controls whether or not the Wrapper should allow gaps in sequences containing numbered components.

• wrapper.ignore_signals (3.0.5)

  Controls whether or not the Wrapper should ignore system signals.

• wrapper.ignore_user_logoffs (3.3.1)

  Controls whether or not the Wrapper will respond to Windows (LogOff) events when running in console mode.

[J]

• wrapper.java.additional.<n> (1.0.0)

  Configures additional Java parameters to pass to Java when it is launched.

• wrapper.java.additional.<n>.stripquotes (1.0.0)

  Tells the Wrapper to automatically strip extra quotes only on UNIX.

• wrapper.java.additional.auto_bits (3.3.5)

  It is often convenient to have this parameter set automatically, when running with 32-bit or 64-bit versions of the Wrapper.

• wrapper.java.additional.auto_bits.<platform> (3.5.15)

  It is possible to activate/deactivate the auto_bits functionality individually on certain supported platforms.

• wrapper.java.additional.default.stripquotes (3.5.17)

  It is possible to change the default strip quotes behavior on UNIX whenever you wish to have the same behavior for all property values.

• wrapper.java.additional_file (3.5.16)

  Provides a way to specify a file which can contain one or more parameters, that will be passed to the JVM when it is launched.

• wrapper.java.additional_file.stripquotes (3.5.16)

  Helps to handle parameters with spaces, since accros platforms they are handle differently.

• wrapper.java.classpath.<n> (1.0.0)

  Helps configuring Java Classpaths to launch your application.

• wrapper.java.classpath.missing.loglevel (3.5.26)

  The Wrapper will log warnings about any missing classpath elements at the DEBUG log level.

• wrapper.java.classpath.use_environment (3.4.1)

  Configures whether the Wrapper passes the generated classpath to the JVM on the Java command line or by setting the CLASSPATH environment variable.

• wrapper.java.command (1.0.0)

  This property is used when launching a JVM.

• wrapper.java.command.resolve (1.0.0)

  Specifies whether the Wrapper should try to resolve the specified Java command or continue using the unresolved path as possibly defined.

• wrapper.java.command.loglevel (3.1.2)

  Configures different log levels at which the generated Java command lines will be logged by the Wrapper.

• wrapper.java.detect_debug_jvm (3.3.6)

  This property enables/disables debugging checks, ignoring certain timeouts.

• wrapper.java.errfile (3.5.8)

  Redirects output from the stderr of the Java process to a file if the JVM has been detached.

• wrapper.java.idfile (3.2.0)

  It can be useful to external applications which need to monitor the Java process's state.

• wrapper.java.idfile.umask (3.2.0)

  Specifies the umask to use when creating the Java id file.

• wrapper.java.initmemory (1.0.0)

  Configures the initial amount of memory in megabytes that the JVM should allocate at startup.

• wrapper.java.initmemory.percent (3.3.0) (Std/Pro)

  Configures a percentage value between 1 and 100 which will translate into a size in megabytes.

• wrapper.java.library.path.<n> (2.2.9)

  Specifies a list of directories and looks for a native (JNI) library used by the application.

• wrapper.java.library.path.append_system_path (3.1.0)

  If a path is needed, this property will cause the Wrapper to append the contents of the system PATH to the Java library path used to launch the JVM.

• wrapper.java.mainclass (1.0.0)

  Class to execute when the Wrapper starts the application.

• wrapper.java.maxmemory (1.0.0)

  Configures the maximum amount of memory in megabytes that the JVM will be allowed to use.

• wrapper.java.maxmemory.percent (3.3.0) (Std/Pro)

  Configures percentage values between 1 and 100 which will translate into a size in megabytes.

• wrapper.java.outfile (3.5.8)

  Redirects stdout of the Java process to a file if the JVM has been detached.

• wrapper.java.pidfile (3.0.5)

  The pid of the Java process will be written to a specific location when the process is launched.

• wrapper.java.pidfile.umask (3.2.0)

  Specifies the umask to use when creating the Java pid file.

• wrapper.java.cpu_affinity.set (3.5.27) (Pro)

  Defines whether the processor affinity feature is enabled for the JVM process.

• wrapper.java.cpu_affinity.default (3.5.27) (Pro)

  Enables or disables by default all CPUs of the machine for the JVM process.

• wrapper.java.cpu_affinity.<n> (3.5.27) (Pro)

  Overrides wrapper.cpu_affinity.default and enables or disables a specific CPU for the the JVM process.

• wrapper.java.cpu_affinity.strict (3.5.27) (Pro)

  Defines if the wrapper should stop when the CPU affinity configuration of the JVM process causes an exception.

• wrapper.java.statusfile (3.2.0)

  The latest status of the Java process will be written to the specified location when is first launched and then whenever the internal status changes..

• wrapper.java.statusfile.umask (3.2.0)

  Specifies the umask to use when creating the Java estatus file.

• wrapper.java.tmpdir.<x> (3.5.0)

  This is often used for caching downloaded files or remote jars, etc.

• wrapper.java.tmpdir.required (3.5.0)

  Controls what the Wrapper should do when it detects the Java temporary directory can not be written to.

• wrapper.java.tmpdir.warn_silently (3.5.0)

  Controls how the Wrapper should notify the user that the Java temporary directory could not be written to.

• wrapper.java.umask (3.2.0)

  Specifies the default umask of the Java process, and thus of any files created by the Java application

• wrapper.java.version.output (3.5.17)

  Displays the exact version of the JVM being used before the application is started.

• wrapper.javaio.buffer_size (3.5.21)

  Controls the size of the buffer used by the pipe between the JVM and Wrapper processes.

• wrapper.javaio.use_thread (3.5.21)

  Controls whether the Wrapper uses a dedicated thread to process console output from the JVM.

• wrapper.jvm_cleanup.timeout (3.4.0)

  Configures the maximum number of seconds to allow the Wrapper to cleanup after a JVM that has been completely shutdown.

• wrapper.jvm_detach_started (3.5.8)

  Configures the JVM to be left running as a standalone process and then the Wrapper will exit.

• wrapper.jvm_exit.timeout (2.2.8)

  Configures the number of seconds allowed for the JVM to report it stopped, and the JVM process actually terminates.

• wrapper.jvm_kill.delay (3.5.6) (Pro)

  Controls the number of seconds to pause between firing a JVM kill event and actually killing it.

• wrapper.jvm.port (3.2.0)

  Configures the port that the JVM will use to connect back to the Wrapper.

• wrapper.jvm.port.max (3.2.0)
• wrapper.jvm.port.min (3.2.0)

  Controls the min/max range of ports that the Wrapper will use when choosing a port.

[L]

• wrapper.lang (3.5.0) (Std/Pro)

  Specifies the output language of the Wrapper.

• wrapper.lang.encoding (3.5.0) (Std/Pro)

  Specifies the encoding of the Wrapper process.

• wrapper.lang.folder (3.5.0) (Std/Pro)

  Sets the location of the language files.

• wrapper.lang.domain (3.5.0) (Std/Pro)

  Sets the domain of the binary and the library mo files

• wrapper.license.debug (3.4.0) (Std/Pro)

  This will cause the Wrapper to dump information about the License Keys that it is locating while being initialized.

• wrapper.license.dev_application (3.3.0) (Std/Pro)
• wrapper.license.features (3.3.0) (Std/Pro)
• wrapper.license.host_id (3.3.0) (Std/Pro)
• wrapper.license.id (3.3.0) (Std/Pro)
• wrapper.license.key.<n> (3.3.0) (Std/Pro)
• wrapper.license.lease_term.begin_date (3.3.0) (Std/Pro)
• wrapper.license.lease_term.end_date (3.3.0) (Std/Pro)
• wrapper.license.licensee (3.3.0) (Std/Pro)
• wrapper.license.type (3.3.0) (Std/Pro)
• wrapper.license.upgrade_term.begin_date (3.3.0) (Std/Pro)
• wrapper.license.upgrade_term.end_date (3.3.0) (Std/Pro)

  Detailed explanation for the license key's properties.

• wrapper.listener.force_stop (3.3.2)

  Controls whether or not the method WrapperListener.stop is called on shutdown.

• wrapper.lockfile (3.2.0)

  Configures a lock file containing the Wrapper's process ID.

• wrapper.lockfile.umask (3.2.0)

  Specifies the umask to use when creating the lock file.

• wrapper.log.lf_delay.threshold (3.5.10)

  Configures the maximum amount of time that will be allowed between the beginning and the end of a log line of output before is logged.

• wrapper.log.warning.threshold (3.5.8)

  The Wrapper will measure how long each individual logging log takes.

• wrapper.logdialog.enable (3.3.1) (Std/Pro)

  Controls whether or not the log dialog should be displayed on shutdown when the version of the Wrapper exits in an error state.

• wrapper.logdialog.format (3.3.1) (Std/Pro)

  Configures the format for logging to the log dialog using tokens.

• wrapper.logdialog.lines (3.3.1) (Std/Pro)

  Controls the maximum number of output lines of the dialog display.

• wrapper.logdialog.loglevel (3.3.1) (Std/Pro)

  Log level to use for logging to the log dialog.

• wrapper.logfile (1.0.0)

  Log file to which all output of the console will be logged.

• wrapper.logfile.close.timeout (3.5.21)

  Controls the number of seconds at which the log file should close after the last log entry.

• wrapper.logfile.flush.timeout (3.5.21)

  The Wrapper will only flush output to the log file after a configurable interval or whenever the system output buffer is full.

• wrapper.logfile.format (2.2.5)

  Configures the format to use for logging to the log file using tokens.

• wrapper.logfile.inactivity.timeout (3.2.0(Deprecated as of 3.5.21))
• wrapper.logfile.loglevel (2.2.5)

  Configures log levels to be used for logging to the log file.

• wrapper.logfile.maxfiles (2.2.5)

  Controls the maximum number of rolled files, by preserving a maximum of 3 files plus the current one.

• wrapper.logfile.maxsize (2.2.5)

  The log file can be set to roll when the file reaches a specified size.

• wrapper.logfile.purge.pattern (3.3.8)

  Controls the file pattern to purge old log files.

• wrapper.logfile.purge.sort (3.3.8)

  Configures sorting modes for log files and decide which files to purge.

• wrapper.logfile.rollmode (3.2.0)

  Controls the rolling of the log file using different modes.

• wrapper.logfile.umask (3.2.0)

  Specifies the umask to use when creating the log file.

[M]

• wrapper.max_failed_invocations (2.2.8)

  Configures the number of times the Wrapper will attempt to restart the JVM.

• wrapper.monitor_thread_count (3.2.0 (Deprecated as of 3.2.1))
• wrapper.max_hostid_timeout (3.4.0) (Std/Pro)

  Configures the maximum number of seconds the Wrapper should wait for Network Interfaces to come up.

[N]

• wrapper.name (3.3.0)

  Configures the service name and used in error messages, events, etc.

• wrapper.native_library (3.1.0)

  Is required that a native library be loaded to be able to handle system signals and perform other functions.

• wrapper.ntservice.account (3.0.0)

  Configures the account to use when running the service.

• wrapper.ntservice.account.prompt (3.5.5)

  The Wrapper will ask the user to input the domain, account name and password in order to install the Wrapper as Windows Service.

• wrapper.ntservice.console (3.1.0)

  Causes the Wrapper to allocate and display a console window when running as a Windows Service.

• wrapper.ntservice.dependency.<n> (1.0.0)
• wrapper.ntservice.description (2.2.5)

  Displays the service description when an application is installed.

• wrapper.ntservice.displayname (1.0.0)

  Displays the name of the service when an application is installed.

• wrapper.ntservice.generate_console (3.3.2)

  Added to force the Wrapper to always create an internal console when running as a Windows Service.

• wrapper.ntservice.hide_console (3.0.4)

  As the Wrapper must create a console for the JVM and appears as an unresponsive console, it's hidden by default.

• wrapper.ntservice.interactive (3.0.0)

  Makes it possible for the service to display a GUI and have access to the desktop when run as a service.

• wrapper.ntservice.load_order_group (3.0.4)

  Specifies the name of the load ordering group of which the service will be a member.

• wrapper.ntservice.name (1.0.0)

  Configures the Service Name on Windows when an application is installed.

• wrapper.ntservice.password (3.0.0)

  Configures the password, and the option to leave this value blank.

• wrapper.ntservice.password.prompt (3.2.0)

  Users will be asked for a password when installing the Wrapper as a service.

• wrapper.ntservice.password.prompt.mask (3.2.0)

  Prevents your password to be displayed in the console.

• wrapper.ntservice.pausable (3.2.1 (Deprecated as of 3.5.0))
• wrapper.ntservice.pausable.stop_jvm (3.2.1 (Deprecated as of 3.5.0))
• wrapper.ntservice.preshutdown (3.5.30)

  Specifies that the service will accept PRESHUTDOWN notifications.

• wrapper.ntservice.preshutdown.timeout (3.5.30)

  Tells the service control manager how long to wait until a service listening to PRESHUTDOWN notifications will stop.

• wrapper.ntservice.process_priority (2.2.7)

  Specifies the priority at which the Wrapper and its JVM will be run at when run as a Windows Service or as a console application.

• wrapper.ntservice.recovery.reset (3.5.5) (Std/Pro)

  A failure count reset can be configured, the Service Manager will reset the counter back to 0 (zero).

• wrapper.ntservice.recovery.command (3.5.5) (Std/Pro)

  Used to configure things like performing cleanups or send an external command in response to a failure.

• wrapper.ntservice.recovery.reboot_msg (3.5.5) (Std/Pro)

  Used to define the text of the message generated with information about why the system was rebooted.

• wrapper.ntservice.recovery.<n>.failure (3.5.5) (Std/Pro)

  Sets the failure action which should happen if the Wrapper service crashes or exits with an error.

• wrapper.ntservice.recovery.<n>.delay (3.5.5) (Std/Pro)

  Configures the time in seconds the Service Control Manager will wait until it actually performs the specified action.

• wrapper.ntservice.starttype (1.0.0)

  Configures Start Modes in which the service is installed.

[O]

• wrapper.on_exit.<n> (3.1.0)

  Configures to restart the application in the event that it exits with certain exit codes.

[P]

• wrapper.pausable (3.5.0)

  Enables the PAUSE and RESUME actions related with some properties.

• wrapper.pausable.stop_jvm (3.5.0)

  Controls what happens when the Wrapper is paused using pausable actions.

• wrapper.pause_on_startup (3.5.5)

  This will cause the Wrapper to go immediately into a paused state, without ever launching a JVM.

• wrapper.pidfile (Usage changed in 3.0.5)

  The Wrapper's process ID will be written in this file.

• wrapper.pidfile.strict (3.5.14)

  Tells the Wrapper to check if the pid file does exists, before it tries to write its pid file.

• wrapper.pidfile.umask (3.2.0)

  Specifies the umask to use when creating the pid file.

• wrapper.ping.alert.loglevel (3.5.16)

  Specifies at which log level the ping alert messages will be logged in the log file.

• wrapper.ping.alert.threshold (3.5.16)

  Specifies that the Wrapper should log a warning in the log file whenever a ping response of the JVM takes longer that a number of seconds.

• wrapper.ping.interval (3.0.5)

  Configures the number of seconds for the interval between the Wrapper ping requests to the JVM.

• wrapper.ping.interval.logged (3.2.4)

  Configures the number of seconds for the interval between Wrapper ping requests which will be logged.

• wrapper.ping.timeout (1.0.0)

  Configures the number of seconds to allow between the Wrapper pinging the JVM and the response from the JVM.

• wrapper.ping.timeout.action (3.5.16)

  Allows to specify a certain action, which will be performed whenever a ping timeout takes place.

• wrapper.port (1.0.0)

  Allows the configuration of a port, which the Wrapper uses to communicate with its Java component running inside a JVM.

• wrapper.port.address (3.5.18)

  Specifies the interface to which the port(s), for communication of the Wrapper with the JVM, should be bound to.

• wrapper.port.max (3.2.0)
• wrapper.port.min (3.2.0)

  Controls the min/max range of ports that the Wrapper will use when choosing a port.

• wrapper.properties.dump.loglevel (3.5.30)

  Controls the log level at which the configuration properties will be logged.

• wrapper.property_warning.loglevel (3.5.21)

  Controls log level warnings about property values that will be logged.

[R]

• wrapper.registry.java_home (3.2.4)

  The Wrapper can be configured to launch a JVM that has been configured in the Windows registry.

• wrapper.request_thread_dump_on_failed_jvm_exit (2.2.7)

  Tells the Wrapper to attempt to request a Thread Dump whenever the JVM does not exit when requested.

• wrapper.request_thread_dump_on_failed_jvm_exit.delay (3.5.6)

  Delays a Thread Dump before the Wrapper actually kills the JVM process.

• wrapper.restart.delay (2.2.9)

  Controls the number of secongs to pause bewteen a JVM exiting and a new JVM being launched.

• wrapper.restart.reload_configuration (3.2.0)

  Controls whether or not the Wrapper configuration file will be reloaded in the event of a JVM restart.

[S]

• wrapper.share.<n>.target (3.5.0) (Std/Pro)

  Sets the target on the local machine to which the resource specified whould get mapped to.

• wrapper.share.<n>.location (3.5.0) (Std/Pro)

  Sets the location of resource such as the Windows Share or Network Printer in UNC format.

• wrapper.share.<n>.type (3.5.0) (Std/Pro)

  Specifies the type of network resource to connect to.

• wrapper.share.<n>.account (3.5.0) (Std/Pro)

  Speicified if users want to connect to a Network Resource using other credentials than the user name or account assigned by default.

• wrapper.share.<n>.password (3.5.0) (Std/Pro)

  This property sets the password affiliated to an assigned account.

• wrapper.share.<n>.startup.failure (3.5.0) (Std/Pro)

  Defines the behavior of the Wrapper if any general error occured.

• wrapper.share.<n>.startup.premapped (3.5.0) (Std/Pro)

  Specifies what the Wrapper will do if a share couldn't be mounted because the Network Resource already existed.

• wrapper.share.<n>.startup.max_retries (3.5.0) (Std/Pro)

  Defines how many times the Wrapper should try to mount a Network Drive, if a network based error occured.

• wrapper.share.<n>.startup.retry_interval (3.5.0) (Std/Pro)

  Specifies the interval in seconds the Wrapper will wait until it retries to mount a Network Drive.

• wrapper.share.<n>.shutdown.unmap (3.5.0) (Std/Pro)

  Specifies if the Wrapper should disconnect the Network Drive at shutdown of the Wrapper.

• wrapper.share.<n>.shutdown.unmap.force (3.5.0) (Std/Pro)

  Specifies whether the disconnection should occur if there are open files or jobs on the connection.

• wrapper.shutdown.timeout (2.2.7)

  Configures the number of seconds allowed between the time the Wrapper asks the JVM to shutdown and the time the JVM responds that it is stopping.

• wrapper.signal.mode.hup (3.2.2)

  Controls what the Wrapper should do whenever HUP signals are received based on configured valid modes.

• wrapper.signal.mode.usr1 (3.2.4)

  Controls what the Wrapper should do whenever USR1 signals are received based on configured valid modes.

• wrapper.signal.mode.usr2 (3.2.4)

  Controls what the Wrapper should do whenever USR2 signals are received based on configured valid modes.

• wrapper.single_invocation (3.1.2)

  Controls to allow a given application to have a single invocation or multiple invocations at the same time.

• wrapper.single_invocation.notify (3.5.28) (Std/Pro)

  Notify for any attempt made to launch a second instance. This will trigger an event and attempt to set focus to the Java application.

• wrapper.single_invocation.notify.focus_window (3.5.28) (Std/Pro)

  Make it possible to set the focus to the top window of the Java application

• wrapper.single_invocation.notify.timeout (3.5.28) (Std/Pro)

  Configures the number of seconds allowed for the Wrapper to take action in response to a second invocation.

• wrapper.single_invocation.notify.show_splashscreen (3.5.28) (Std/Pro)

  Make it possible to hide or show the splashcreen when a second instance is launched in single invocation mode.

• wrapper.splashscreen.mode (3.3.7) (Std/Pro)

  Allows to set the display mode of the splash screen displayed when running the consoleless version of the Wrapper binary.

• wrapper.startup.delay (3.1.0)

  Controls the number of seconds to pause between the Wrapper and the first JVM being launched.

• wrapper.startup.delay.service (3.1.0)

  Configures a startup delay when running as a Windows Service or a console application.

• wrapper.startup.delay.console (3.1.0)

  Configures a startup delay when running as a console application.

• wrapper.startup_thread.timeout (3.5.11)

  Configures the number of seconds to allow asynchronous startup operations to be completed.

• wrapper.startup.timeout (1.0.0)

  Configures the time when the JVM's process is launched and the time the Wrapper's JVM responds that the application has started.

• wrapper.statusfile (3.2.0)

  File to write the current Wrapper status to.

• wrapper.statusfile.umask (3.2.0)

  Specifies the umask to use when creating the status file.

• wrapper.successful_invocation_time (2.2.8)

  Configures the minimum amount of time that an application must remain running.

• wrapper.syslog.facility (3.2.1)

  Customizes facility values when logging to the syslog on UNIX systems.

• wrapper.syslog.ident (3.2.0)

  Used to specifiy the identity field used in syslog entries.

• wrapper.syslog.ident.enable (3.5.28)

  Used to tell the Wrapper whether to create an event source for the Windows event log.

• wrapper.syslog.local.host (3.5.0)

  Specifies the local host name which is included in the packets being sent.

• wrapper.syslog.loglevel (2.2.5)

  Configures log levels for logging to the Event Log on Windows systems, or the syslog on UNIX systems.

• wrapper.syslog.remote.host (3.5.0)

  Used to tell the Wrapper to redirect all of its syslog output to a remote host.

• wrapper.syslog.remote.port (3.5.0)

  Specifies the port that the remote syslog server is listening on.

• wrapper.syslog.split_messages (3.5.24)

  Messages are forced to be broken up into individual lines making them easier to read.

[T]

• wrapper.thread_count_delay (3.2.0 (Deprecated as of 3.2.1))
• wrapper.thread_dump_control_code (3.3.0)

  The Wrapper is able to initiate a thread dump in response to a user defined control code.

• wrapper.timer.<n>.action (3.3.0) (Pro)

  Configures different actions using specific values.

• wrapper.timer.<n>.interval (3.3.0) (Pro)

  Timer intervals can be built up using a combination of tokens.

• wrapper.timer.max_catchup (3.3.0) (Pro)

  Configures the maximum amount of time at which events are allowed to be fired catching up with time zone changes.

• wrapper.timer_fast_threshold (3.1.0)

  Displays a message to the log whenever the system time falls behind the (tick) timer by more than a threshold number of seconds

• wrapper.timer_slow_threshold (3.1.0)

  Displays a message to the log whenever the (tick) timer falls behind the system time by more than a threshold number of seconds

• wrapper.timezone (3.3.6) (Std/Pro)

  Defines the timezone where the Wrapper will be executed.

• wrapper.timezone.debug_timestamps (3.5.30) (Std/Pro)

  Displays debugging informations in the timestamps of the log outputs.

• wrapper.timezone.folder (3.5.29) (Std/Pro)

  Specifies the path to a directory containing the IANA Time Zone Database source files.

• wrapper.timezone.use_summer_time (3.3.7) (Std/Pro)

  Disables the Daylight saving time (summer time) whenever you have servers in different timezones.

[U]

• wrapper.umask (3.2.0)

  Sets the permission used when creating files.

• wrapper.use_javaio_thread (3.5.8)

  Controls whether the Wrapper uses a dedicated thread to process console output from the JVM.

• wrapper.use_system_time (3.1.0)

  Controls internally how the Wrapper manages the time and scheduling of events.

[W]

• wrapper.working.dir (3.1.0)

  Configuring the Working Directory.

• wrapper.wait_for_hostid (3.4.0) (Std/Pro)

  Enables the Wrapper to wait for the host Id at startup.

转载于:https://my.oschina.net/piorcn/blog/711865