World Map
Java Service Wrapper is the easiest way to make your product more reliable.
  • Free Trial
  • Buy Now
wrapper.use_javaio_thread Property

wrapper.use_javaio_thread

Compatibility :3.5.8 (Deprecated as of 3.5.21)
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSXLinuxIBM AIXFreeBSDHP-UXSolarisIBM z/OSIBM z/Linux

WARNING

Use of this property has been deprecated as of Wrapper version 3.5.21 in favor of the new wrapper.javaio.use_thread property.

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 drawbacks of using a dedicated thread are :

  • slighly higher memory and resource requirements, and
  • that 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.

Example:
wrapper.use_javaio_thread=FALSE

Reference: Command File