ActiveVOS Server Console Help
Select the Eventing Service page from the Admin>Configure Services menu. The settings displayed on this page are for configuration of the ActiveVOS business event processing manager. Developers create and deploy event statements and patterns that process data to find out interesting trends about running or completed BPEL processes.
ActiveVOS business event processing is based on Esper, an event stream processing language and engine. All Esper events are processed asynchronously from the process firing the events, so there is a thread pool with a dedicated event queue where the events are stored until the thread or threads in the pool servicing that queue can load those events into Esper.
When the event manager is running on a clustered server, there is a thread pool for each node in the cluster and each thread pool has its own queue for Esper events.
The statistics on this page are displayed to provide some information about the status of each queue in the pools.
The following configuration settings are available. Starting with “Max pool size” the settings are configurable.
|
Pool Id |
The name of the ThreadPool. The name is ThreadPool_N where N represents the engine Id of the node in the cluster. |
|
Event Queue Size |
The number of unprocessed events currently in the queue |
|
% Free |
The % of capacity remaining in the queue |
|
Max pool size |
Determines what the maximum number of threads that could service the event queue should be. The default is one. Setting this property to a number greater than one may cause the events to be processed into Esper in a different order in which they were fired. This processing order may or may not matter, depending on the statements and patterns registered. |
|
Core pool size |
The number of threads that are always available to service the queue. The default is one. If the core size is two, and the max pool size is four, then there will always be two threads processing the event queue unless a 3rd and 4th event are queued in which case the thread pool grows to the max size. |
|
Thread keep-alive |
The number of milliseconds that any threads created above the core pool size will live before they are terminated. The default is 60000. |
|
Max queue size |
The maximum number of events the event queue holds before Esper events are rejected. The default is 10000. |
|
Debugging enabled |
An indicator flag to show if the event manager is currently printing debug information into the server log or console |
Stopping and Restarting the Esper Event Manager
The Restart button allows the event manager settings to take effect without an ActiveVOS server restart. Also, the Restart button can be used anytime you want Esper to be refreshed to a state where it looks like the event manager was just restarted.
Copyright (c) 2004-2009 Active Endpoints, Inc.