wrapper.disable_tests
Compatibility :3.5.16
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSXLinuxIBM AIXFreeBSDHP-UXSolarisIBM z/Linux

The WrapperManager class contains several methods that are very useful for testing the Wrapper's failure modes, but they can pose a security risk if untrusted code were to call them in a running system.

The Wrapper has supported the use of a Security Manager to control access to these and other functionalities since very early versions. However, the Security Manager is deprecated in recent versions of Java and is often not used by programmers.

It is possible to disable these test methods with the wrapper.disable_tests property.

The test methods are disabled by default with a value of "TRUE".

WARNING

Prior to version 3.6.3, the default value of this property was "FALSE".

Test methods are almost never needed for normal applications and could cause security or stability problems, so it is recommended to disable them in production (by adding wrapper.disable_tests=TRUE to your configuration file).

Example: 
wrapper.disable_tests=FALSE

This property affects the use of the following methods:

If any of the testing methods are called when tests have been disabled, they will cause an IllegalStateException to be thrown.

Example calling disabled test: 
jvm 1    | Exception in thread "main-myapp-thread" java.lang.IllegalStateException: Test methods have been disabled.
jvm 1    |      at org.tanukisoftware.wrapper.WrapperManager.accessViolationNative(WrapperManager.java:2699)
jvm 1    |      ...
jvm 1    |      ...

NOTE

When tests are enabled, the Wrapper will print a warning before starting the JVM. The log level of this warning can be controlled with the wrapper.java.tests.warning.loglevel property.