Compatibility :	3.5.21
Editions :
Platforms :

This property controls whether the Wrapper uses a dedicated thread to process console output from the JVM. Traditionally all such output has been processed within the Wrapper's main thread. However, on heavily IO loaded servers, this can cause the main thread to block while log output is being written to disk.

Unless the Wrapper's DEBUG log level has been set, the main loop does not do much logging other than the JVM console output so moving this output into another thread can help make sure that the Wrapper's main thread is always able to run without any delays.

The dedicated thread also allows the Wrapper to process pending Java output with much less delay.

If the buffer of the pipe between the JVM and the Wrapper becomes full then the JVM will block until the Wrapper has a chance to process the pending console output. If your application is logging very long lines or very large amounts of output then you may benefit from increasing the default pipe buffer size. See the wrapper.javaio.buffer_size property for more information.

Note that there is a lot of overhead by the system to render console log output. This is especially true on Windows. If your application is experience performance issues logging large amounts of console output, we recommend either reducing the log output or disabling the console log output by setting the wrapper.console.loglevel property to STATUS.

The drawbacks of using a dedicated thread are:

• Slighly higher memory and resource requirements.
• The debug log output especially on startup can be a little harder to read because entries logged by the two threads are not nicely in sync.

The default value is "FALSE" as most users do not require the dedicated thread.

wrapper.javaio.use_thread=FALSE

• wrapper.console.direct (3.5.21)

  Specifies whether the Wrapper will use Windows APIs or pipes to write console log outputs.

• wrapper.console.flush (3.2.0)

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

• wrapper.console.format (1.0.0)

  Configures the format of outputs sent to the console.

• wrapper.console.loglevel (1.0.0)

  Filters messages sent to the console according to their log levels.

• wrapper.console.fatal_to_stderr (3.5.3)
• wrapper.console.error_to_stderr (3.5.3)
• wrapper.console.warn_to_stderr (3.5.3)

  Controls whether warning messages sent to the console are logged through stdout or stderr.

• wrapper.console.title (3.1.0)

  Sets the title of the console in which the Wrapper is running.

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

  Set the console title per platform.

• wrapper.disable_console_input (3.3.2)

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

• wrapper.ntservice.console (3.1.0)
• wrapper.ntservice.generate_console (3.3.2)
• wrapper.ntservice.hide_console (3.0.4)
• wrapper.ntservice.interactive (3.0.0)
• 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.commandfile (3.2.0)

  Sets the path to a file containing commands to be executed.

• wrapper.commandfile.enable_tests (3.5.0)

  Enables test commands.

• wrapper.commandfile.poll_interval (3.5.31)

  Specifies time intervals to use when testing the existence of command file.

• wrapper.command.poll_interval (3.2.0, deprecated as of 3.5.31)

  Specifies time intervals to use when testing the existence of command file.

• 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.

• wrapper.pausable (3.5.0)

  Enables the PAUSE and RESUME actions.

• wrapper.logfile.loglevel (2.2.5)

  Filters messages sent to the log file according to their log levels.

• wrapper.console.loglevel (1.0.0)

  Filters messages sent to the console according to their log levels.

• wrapper.syslog.loglevel (2.2.5)

  Filters messages sent to the syslog (or event log on Windows) according to their log levels.

• wrapper.use_system_time (3.1.0)

  Uses the system time (instead of a background timer thread) for all internal timekeeping functions of the Wrapper.

• wrapper.javaio.use_thread (3.5.21)

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