...
AsynchronousEventHandler
StuckAlertEvents aren't dispatched via the engine's regular event handler because in this case the handler itself may be stuck. To receive AepStuckAlertEvents, and application must register an AsynchonousEventHandler with the engine via the setAsynchronousEventHandler method.
AepStuckAlertEvent
The following accessors are available on a AepStuckAlertEvent
| Field | Description |
|---|---|
| Reason | Returns the reason for this alert. Possible values are: HungTransactionPipeline: AepEngine transactions complete asychronously in a pipelined fashion. The engine's pipeline is considered hung when there are oustanding commits that have not completed. HungEventHandler :Indicates that the AepEngine's event processor is hung. The event processor thread handles dispatching of application messages to their handlers along with other internal events. |
| Message | An optional descriptive message intended for display in an alert message. |
| Engine | The engine that is stuck. |
| LastEventProcessedTimestamp | Gets the timestamp in millis of the last event fully processed by the engine's event handler or the time that the first event was received whichever is greater |
| LastCommitCompletionTimestamp | Gets the timestamp in millis of the last completed engine transaction or the timestamp that the first event was received whichever is greater |
| IncompleteCommitCount | Gets the number of commits that have not been completed. |
Because this alert is not dispatched on the engine's event handler, most of the engine's methods can't be used in a threadsafe fashion. Only engine methods that are explicitly indicated as being threadsafe are permissible.