Index |
|
wrapper.jvm_detach_started |
||||||||
Some users have expressed the desire to be able to make use of the Wrapper as a simple launching mechanism for Java. This property can be used to detach the JVM from the Wrapper as soon as it has completed the startup process of the application. The JVM will then be left running as a standalone process and the Wrapper will exit. The JVM will be detached when this property is set to TRUE. As the Wrapper stays attached until the JVM has reported that the application is started, this makes it possible to log any startup problems into the usual Wrapper log file. As the Wrapper will shutdown once the Java application is started, none of the Wrapper standard monitoring or recovery features will be available. The native library of the Wrapper will still be usable however so those functions will work correctly. By design, this will only work when the Wrapper is not being run as a Windows Service or UNIX Daemon process. If Java were to be detached when running as a service, then there would be no way to shutdown the JVM. The default value is "FALSE".
Once a JVM has been detached, its stdout and stderr are by default thrown away.
If you need to capture them for debugging purposes, it is possible to redirect
the output to files using the
wrapper. |
wrapper.java.outfile |
||||||||
It is possible to redirect the stdout of the Java process to a file if the
JVM process has been detached. If any file is not specified, then the stdout is simply
thrown away. This property has no effect unless the JVM has been detached
with wrapper.
|
wrapper.java.errfile |
||||||||
It is possible to redirect the stderr of the Java process to a file if the
JVM process has been detached. If any file is not specified, then the stderr is simply
thrown away. This property has no effect unless the JVM has been detached
with wrapper.
|