wrapper.disable_tests
Compatibility :3.5.16
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSXLinuxIBM AIXFreeBSDHP-UXSolarisIBM z/OSIBM 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, it is also possible to disable these test methods with the wrapper.disable_tests property.

Any JVM that is running untrusted code should implement a Security Manager, so it is normally safe to leave this property with its default value.

The test methods are enabled by default with a value of "FALSE".

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    |      ...