A wide variety of Java applications make use of Java's temporary directory, directly or indirectly.
It often used for caching downloaded files or remote jars, etc.
Most of the time, the default Java temporary directory will work correctly.
There are times where the system's file system privileges make it impossible for the Wrapper to
write to this directory however. One example of this is running as a Service as
the default SYSTEM user under Windows, starting with Windows Vista or 2008.
In such cases, Java's default temporary directory resolves to the locked down directory:
Controls what the Wrapper does when it detects, on startup,
that the Java temporary directory can not be written to.
When TRUE, the Wrapper will exit the JVM with error code 1.
The default value is "FALSE" for backwards compatibility.
Controls how the Wrapper notifies the user that the Java temporary directory could not be written to.
A message will always be written to the log when debug output is enabled.
However, only when this property is FALSE will the user see a message with debug output disabled.
The default value is "TRUE" for backwards compatibility.
Even though this message is very useful, it is silent by default
because virtually all Windows users would see the error on Vista and above
when running their service as the default SYSTEM user
unless they have specifically defined a custom temp directory.