Administrator

Event Handling Threads

Event generation and processing is an integral part of the underlying Mobiliser framework.

Thread Pool

The default values for the number of event-handling threads can create a situation where the events generated during a transaction are processed after the transaction.  Using the default values can reduce database load to a minor degree, but if a server restart is necessary, might also require regenerative event processing. You can largely avoid this effect by using the built-in autodetect logic when sizing the event-handling thread pools. In a high-throughput scenario, using this logic generally leads to more consistent load patterns.

Preferences path: <SMP_HOME>\Server\config_master\com.sybase365.mobiliser.framework.event.core.properties

Requires server restart to take effect: Yes

You can set these configuration options:
Variable Default Value Modified Value
regeneration.batch.size 10 1024 * CPU cores
delayedq.capacity 1000 65536 * CPU cores
processq.capacity 1000 65536 * CPU cores
catchupq.capacity 1000 65536 * CPU cores

Handler

Each event handler has two private variables that you can set as needed.

Configuration location: Multiple locations

Requires server restart to take effect: No

You can set these configuration options in preferences:
Variable Default Value Modified Value
event.handler.maxActive Varies –1 (infinity)
event.handler.maxIdle Varies –1 (infinity)