• Configuration Property Overview
• Property List by Category
• Property List by Name
• Advanced Properties

Compatibility :	3.2.0
Editions :
Platforms :

WARNING

DO NOT modify any of these parameters unless you have read this property description. Incorrect settings can cause the Wrapper to fail to operate as expected.

File to write the current Java id to. This property is not set by default.

This property has no use for most applications. It can be useful to external applications which need to monitor the Java process's state however.

If this property is set, a file containing the latest id of the Java process will be written to the specified location when the first Java process is launched. The id will be incremented by one each time the JVM is restarted. The first invocation will be 1. This is the same value returned by WrapperManager.getJVMId() or displayed in the log file. The file will be deleted when the Wrapper process has terminated.

wrapper.java.idfile=./myapp.java.id

NOTE

The Wrapper needs to be able to open and then write to this file whenever its status is changed. The Wrapper does include code which allows for the file being briefly locked by an external process. However, the Wrapper will fail with a warning in the log if the file remains locked for more that 1 second. This will not affect the operation of the Wrapper.

NOTE

Reloading the configuration will NOT enable to take effect on the value of this property. The Wrapper is required to restart in order to make the changes effective.

Compatibility :	3.2.0
Editions :
Platforms :

You can set "umask" on this file. See the wrapper.*.umask property.

• wrapper.java.pidfile
• wrapper.java.idfile
• wrapper.java.statusfile

• wrapper.pidfile
• wrapper.lockfile
• wrapper.statusfile

If you notice something that is incorrect, missing, or simply feel that some part of this page could be explained better, feel free to log in and add a comment. You will need to register before you can log on.