java.lang.isolate
Class IsolateEvent.Type

java.lang.Object
  |
  +--java.lang.isolate.IsolateEvent.Type

Enclosing class:

IsolateEvent

public static final class IsolateEvent.Type

extends Object

Define the types of an IsolateEvent that can be generated.

See Also:

IsolateEvent.getType()

Field Summary

static IsolateEvent.Type	EXITING The stopping state.
static IsolateEvent.Type	STARTING The starting state.
static IsolateEvent.Type	TERMINATED The terminated state.

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

STARTING

public static final IsolateEvent.Type STARTING

The starting state. A STARTING event results from an isolate's start method being invoked and indicates execution of user code is able to commence. At most one STARTING event will be delivered on behalf of an isolate and no isolate event will be delivered before a STARTING event.

See Also:

Isolate.hasStarted()

EXITING

public static final IsolateEvent.Type EXITING

The stopping state. A EXITING event results from any of several actions that initiate the shut down sequence in an isolate:

• The last non-daemon thread in the associated isolate died.
• The isolate invoked Runtime.exit or Runtime.halt.
• Another isolate invoked Isolate.exit or Isolate.halt on the isolate.
• Some other occurrence (e.g. a signal) initiated the same response as if the isolate invoked Runtime.halt.

At most one EXITING event will be delivered on behalf of an isolate, even if any of the above occur more than once for that isolate. A EXITING event will always be preceded by a STARTING event. Additional code such as shutdown hooks or finalizers may be executed by an isolate after a EXITING event is issued.

See Also:

Isolate.hasExited(), System.exit(int), Runtime.exit(int), Runtime.halt(int), Isolate.exit(int), Isolate.halt(int)

TERMINATED

public static final IsolateEvent.Type TERMINATED

The terminated state. A TERMINATED event is supplied when an isolate has terminated. This event is issued at the point when no additional user code will execute in the associated isolate.

The exit code of the associated isolate is available via the IsolateEvent.getExitStatus() method. The exit status of an isolate defaults to 0 but will be set to the parameter passed to the exit or halt method that terminated the isolate. If such exit methods are invoked multiple times, the exit status may be any one of the provided values, with the restriction that all TERMINATED events report the same value for the associated isolate.

At most one TERMINATED event will be delivered on behalf of an isolate to a particular event link. A TERMINATED event will always be preceded by a EXITING event. Additionally, no more events will be delivered following a TERMINATED event.

See Also:

Isolate.hasTerminated(), System.exit(int), Runtime.exit(int), Runtime.halt(int), Isolate.exit(int), Isolate.halt(int)