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

wrapper.console.direct

Compatibility :3.5.21
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSX (Not Supported)Linux (Not Supported)IBM AIX (Not Supported)FreeBSD (Not Supported)HP-UX (Not Supported)Solaris (Not Supported)IBM z/OS (Not Supported)IBM z/Linux (Not Supported)

When set to TRUE, the Wrapper will make use of Windows APIs to write console log output to the console window. When FALSE, the Wrapper works like UNIX in that it writes the output to the stdout or stderr pipes. Writing to pipes makes it possible to redirect the output into another application. Unfortunately, Windows is very slow at rendering output in the console which is received via a pipe. If you redirect to a file or another application then this rendering speed hit can be avoided. The default value is "TRUE".

Example:
wrapper.console.direct=TRUE

Previous versions of the Wrapper 3.5.21 all made use of the pipe output method. We chose to change the default behaviour so the majority of users would be able to take advantage of these speed increases. You will need to reenable pipe output if and only if you need to be able to redirect the output.

If you are running as a service then a console will normally not exist. The exception is if you have both the wrapper.ntservice.interactive and wrapper.ntservice.console properties set to TRUE.

WARNING

All Java output is sent across into own stdout/stderr pipes to the Wrapper process. If the Wrapper is slow writing to the console or file, then it will also slow down the ability to read output from the Java. If the pipe becomes full because the Wrapper has not read everything then the Java end of the pipe will block trying to write its output. This can have a performance impact on your application, and it is important to be aware of it. Any application will have this problem, including a standalone Java process.

You can alleviate this problem by enabling the wrapper.console.direct property, increasing the size of the pipe buffer with the wrapper.javaio.buffer_size property. It is also possible to completely disable the console output using the wrapper.console.loglevel property.

Reference: Console