About the Framework Event Service
The Framework Event Service is an independent process that can run on any application (utility) server. Each instance of the Framework Event Service monitors the event queue for any number of configurations defined locally.
For load-balancing purposes, this service safely acquires work from the database queue of each configuration's application, so that multiple event services can run on one or multiple servers. The event service monitors the event queue for these events and handlers:
- New events that have been queued by means of asynchronous generation methods or suspending framework events, as found in the Queued Event table
- New event handlers that have been queued by means of the firing of asynchronous event handlers, as found in the Queued Event Handler table
- Resuming event handlers that had been adjourned, and have now completed a Prompt, Wait, or Sleep event action, as found in the Event Handler Status table having a value in Retest At Date that is older than the current date and time
- Resuming event handlers that had been adjourned, and have now completed a Discover File action, as found in the Event Handler Status table having a value in Path To Watch and no value in Last Watched Date
- Running event handlers whose current action has timed out, as found in the Event Handler Status table having a value in Times Out At Date that is older than the current date and time
- Active event triggers
-
Continuing events that have successfully retried a previously failed handler, as found in the Event Status table having a value in Continue After Handler Row Pointer
Administrative details
To eliminate the possibility of deadlocks when manipulating event data, a second database connection is used for event data modifications, that is, separate from the one used by the event action execution methods. Also, any event data modifications that do not need to be available to other processes (any tier of any interactive user session or other event service instances) are made in memory and written only when required.
To avoid overtaxing the application server, the Framework Event Service administrator has control over the minimum interval for these attributes:
- RetestInterval parameter on Wait event actions
- Interval parameter on Sleep event actions
- RetestInterval attributes on event triggers
When any of these attributes is referenced, if the designer-specified value is greater than zero but lower than the minimum interval for the Framework Event Service, the minimum value is used.
The Framework Event Service logs various levels of messages to the Infor framework Log Monitor.