Compatibility :	3.2.0
Editions :
Platforms :

When set to TRUE causes the Wrapper to implicitly flush stdout after each line of output is sent to the console. For normal operation, this does not appear to be necessary. But users who are piping the console output of the Wrapper process into another application have reported that the console output was not being flushed in real time. The default value is "FALSE".

wrapper.console.flush=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.