Managing failed event sequences and unrecoverable events
You can use the WebSphere® Application Server administrative console to manually manage failed event sequences and unrecoverable events.
Before you begin
About this task
When a monitor model is generated using the development toolkit, sequences of events that can be run in parallel are identified. Specific instances of these event sequences are identified by their root instance ID. If an event cannot be processed, the model stops processing all subsequent messages in the event sequence instance (identified by a root instance ID) in which the fault occurred. Other event sequence instances of the model can continue to process incoming events. Manual intervention is therefore required only to restart processing of a particular event sequence instance.
When an event cannot be processed and the root instance ID of its event sequence instance cannot be determined, the event is considered unrecoverable. Unrecoverable events are either missing the information needed to identify the root instance ID of the event sequence instance it belongs to or the model could not parse the incoming event (for example, malformed XML). Unrecoverable events can be inspected in an attempt to establish the cause of a failure, but they cannot be resubmitted.
Managing these failed event sequences or unrecoverable events involves the following tasks.