All Classes and Interfaces
Class
Description
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
ReentrantLocks, which will can be detected and restarted by the Standard
Edition.
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.
A print stream which can be put into a state in which all calls to write
to it will result in the calling threads deadlocking in the call.
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 test is designed to make sure the Wrapper handles the case where the
JVM is restarted while the Wrapper is blocking due to a long disk IO queue.
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.
This test was created to test timeout problems under heavily loaded
conditions.
Test case which launched several threads and lets them run for 30 seconds.
Test case which launched several threads and lets them run for 30 seconds.
This is a Test / Example program which can be used to test the
main features of the Wrapper.
This is a simple test to see how the WrapperManager behaves when a main
class designed for Integration Method #3 is called using Integration
Method #2.
Tests Bug #531880 where % characters in the text output were causing
the wrapper to crash.
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 is a very simple test of how a main class using Integration Method #3
works.
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 the Wrapper works correctly when stop or restart is
called before the start method has completed.
This test is to make sure that property values set in the wrapper config file
are handled and passed into the JVM as expected.
This test is designed to make sure the Wrapper handles the case where the
JVM is restarted while the Wrapper is blocking due to a long disk IO queue.
If an application instantiates an instance of this class, the JVM will
listen on the specified port for connections.
WrapperConsumableEvent is used to keep trace whether
the event has been handled or not.
WrapperControlEvent are used to notify the listener whenever the native
wrapper code traps a system control signal against the Java process.
WrapperCoreEvents are used to notify the listener of the internal
workings of the Wrapper.
WrapperEvents are used to notify WrapperEventListeners of various wrapper
related events.
WrapperEventListeners can be registered with the WrapperManager class
to receive WrapperEvents.
WrapperEventPermissions are used to grant the right to register to start
receiving events from the Wrapper.
A WrapperGroup contains information about a group which a user
belongs to.
By default the WrapperJarApp will only wait for 2 seconds for the main
method of the start class to complete.
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.
WrapperLogFileChangedEvent are fired whenever the log file used by the
Wrapper is changed.
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.
WrapperPermissions are used to control access to the various methods of the
WrapperManager class.
WrapperPingEvent are fired each time a ping is received from the Wrapper
process.
A WrapperProcess is returned by a call to WrapperManager.exec and can
be used to reference the new child process after it was launched.
With WrapperProcessConfig Class the startup configuration for the Process
can be passed to the WrapperManager.exec methods.
The InputStream Class of a WrapperProcess, representing all the data the
ChildProcess writes to the Wrapper.
The OutputStream Class of a WrapperProcess, representing all the data the
ChildProcess read from the Wrapper.
A collection of utility methods which make it easy to work with Wrapper
configuration Properties without littering code with error handling.
WrapperRemoteControlEvent are fired when a signal is caught from
outside the Wrapper (for example a signal coming from a pipe).
A resource bundle which is used to help localize applications to the default
locale of the JVM.
WrapperSecondInvocationEvent is fired whenever a second
instance of the Wrapper starts in single invocation mode.
WrapperServicePauseResumeEvents are used to notify the listener that the Wrapper
is requesting that the Java application be paused or resumed.
WrapperServiceControlEvents are used to notify the listener whenever a
Service Control Event is received by the service.
WrapperServiceEvents are used to notify the listener of events related
the service.
WrapperServiceExceptions are thrown when the Wrapper is unable to obtain
information on a requested service.
WrapperServicePauseEvents are used to notify the listener that the Wrapper
is requesting that the Java application be paused.
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.
WrapperServiceResumeEvents are used to notify the listener that the Wrapper
is requesting that the Java application be resumed.
WrapperShuttingDownExceptions are thrown when certain Wrapper functions
are accessed after the Wrapper has started shutting down.
By default the WrapperSimpleApp will only wait for 2 seconds for the main
method of the start class to complete.
By default the WrapperStartStopApp will only wait for 2 seconds for the main
method of the start class to complete.
A collection of utility methods which make it easy to work with System
Properties without littering code with error handling.
WrapperPingEvent are fired each time a ping is received from the Wrapper
process.
A WrapperGroup contains information about a group which a user
belongs to.
A WrapperUser contains information about a user account on the platform
running the Wrapper.
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 WrapperGroup contains information about a group which a user
belongs to.
A WrapperWin32Service contains information about an individual service
registered with the current system.
A WrapperUser contains information about a user account on the platform
running the Wrapper.