Previous Topic

Next Topic

Book Contents

Book Index

System Properties

The OSGi Event Admin Bundle uses the following system properties:

System Property

Type

Default Value

Description

mbs.events.debugTime

int

-

If a non-zero value is specified, for every processing of the event, which takes more time than the specified debugTime, a log entry with level debug with information for the handler and the consumed time will be logged.

mbs.events.watchdog

boolean

true

Enables watchdog support for posted events.

mbs.events.synch.watchdog

boolean

true

Enables watchdog support for sent events.

mbs.events.watchdog.timeout

int

30000

This property makes sense only if mbs.events.watchdog is set to true. It shows the maximum allowed timeout for a handler.

mbs.events.blacklist

boolean

true

This property makes sense only if mbs.events.watchdog is set to true.

Enables blacklisting of handlers, which are too slow i.e. which cannot handle the event in the specified timeout.

mbs.events.handler.ignoreFilterError

boolean

false

If an EventHandler is registered with an invalid filter described in service registration property EVENT_FILTER, then the EventHandler is ignored from the Event Admin and it receives no events from event admin. If the EventHandler is registered with a topic, but the filter is wrong, and if you would like the Event Admin to send the events with matching topic to the EventHandler, set the system property mbs.events.handler.ignoreFilterError to true. This property is read only once at bundle startup.

In order to keep backward compatibility with the previous implementation of the Event Admin in regards to EventHandlers, registered with incorrect filter, the system property has to be set with value true.

mbs.events.collector.enabled

boolean

false

Enables the feature, that caches dispatched events and makes them available to applications installed later. This functionality is optional and allows you to inspect the events, that were sent before you have registered your handler. When enabled, it is configured with proper event limit, discarding the oldest events as provided by the mbs.events.collector.limit property.

mbs.events.collector.limit

boolean

1000

Configures a reasonable event limit – if not set, the value by default is 1000. Then only the last 1000 events are being cached and the older events are discarded.

To access dispatched events that were sent before a handler was registered, set the system property mbs.events.collector.enabled to true.