All Classes and Interfaces

This is test is designed to simulate various deadlock cases using either ReentrantLock instances or synchronized objects.

This is test is designed to simulate a series of deadlock cases using standard Object synchronization, which will can be detected and restarted by the Standard Edition.

This is test is designed to simulate a series of deadlock cases using ReentrantLocks, which will can be detected and restarted by the Standard Edition.

This is a Test / Example program which can be used to test the main features of the Wrapper.

This class tests the ability to write to the output stream of a subprocess and to read the input stream of that same process.

Test case which launched several threads and lets them run for 30 seconds.

Can be run without the Wrapper as: java -classpath lib/wrappertest.jar org.tanukisoftware.wrapper.test.Performance NOTE - This class intentionally does not use resources for localization because it needs to be able to be run without the Wrapper components being loaded.

This test is to make sure the Wrapper handles applications whose stop method take too much time to complete.

This test is to make sure that property values set in the wrapper config file are handled and passed into the JVM as expected.

WrapperConsumableEvent is used to keep trace whether the event has been handled or not.

WrapperCoreEvents are used to notify the listener of the internal workings of the Wrapper.

WrapperEventListeners can be registered with the WrapperManager class to receive WrapperEvents.

A WrapperGroup contains information about a group which a user belongs to.

WrapperJNIErrors are thrown when user code encounters problems accessing native Wrapper features.

Applications which need to be controlled directly as a service can implement the WrapperListener interface and then register themselves with the WrapperManager on instantiation.

WrapperLoggingEvents are used to notify the listener of events related to logging such as updates to the log file name.

Handles all communication with the native portion of the Wrapper code.

Tests the conversion of system time into ticks.

This MBean interface provides access to a number of actions which can be useful for testing how well an application responds to JVM crashes.

WrapperPingEvent are fired each time a ping is received from the Wrapper process.

With WrapperProcessConfig Class the startup configuration for the Process can be passed to the WrapperManager.exec methods.

The OutputStream Class of a WrapperProcess, representing all the data the ChildProcess read from the Wrapper.

WrapperRemoteControlEvent are fired when a signal is caught from outside the Wrapper (for example a signal coming from a pipe).

WrapperSecondInvocationEvent is fired whenever a second instance of the Wrapper starts in single invocation mode.

WrapperServiceControlEvents are used to notify the listener whenever a Service Control Event is received by the service.

WrapperServiceExceptions are thrown when the Wrapper is unable to obtain information on a requested service.

WrapperServicePermissions are used to grant the right to start, stop, pause, continue, interrogate, or send custom codes to other services running on a Windows system.

WrapperShuttingDownExceptions are thrown when certain Wrapper functions are accessed after the Wrapper has started shutting down.

By default the WrapperStartStopApp will only wait for 2 seconds for the main method of the start class to complete.

WrapperPingEvent are fired each time a ping is received from the Wrapper process.

A WrapperUser contains information about a user account on the platform running the Wrapper.

WrapperEventPermissions are used to grant the right to register to start receiving events from the Wrapper.

A WrapperWin32Service contains information about an individual service registered with the current system.