mbs.config.updateTimeout

int

10

Refers to the period in seconds the Config Bundle will wait for a Managed Service (Factory) to process its configuration. Configuration Manager update events can hang while calling a Managed Service or Managed Service Factory updated method. Specifies a time period in seconds during which CM Event Thread must return from an updated method. After this period passes, the Config Bundle stops the running thread and creates a new one to process the events. The minimum allowed value is 1 second.

mbs.config.deleteConfigsOnUninstall

boolean

false

If true, when a bundle is uninstalled the Configuration Manager will delete the configurations stored for that bundle.

mbs.config.storeDBinDataRootDir

boolean

false

If true, the Configuration Manager will place its persistent database into the root directory of its storage area instead of the storage of the DB Bundle.

This property should be set to true if you want to have configuration-related persistent data removed upon uninstalling the Config bundle.

mbs.config.flushDB

boolean

false

If true, each change in the configurations stored by the Configuration Manager will be saved persistently into the database.

mbs.config.debug

boolean

false

Turns on/off debugging to the Log Service or the system output.

mbs.config.console

boolean

false

Specifies that logged entries should be printed to the framework runtime console.

mbs.measurements.full

boolean

false

Turns on/off logging the startup time of the Config Bundle's functional parts.

mbs.measurements.bundles

boolean

mbs.config.unboundCheck.disabled

boolean

false

When set to true disables the check, whether there is still an installed bundle for each loaded configuration from the DB. Otherwise by default such a check is made once per every configuration on every framework restart.

It helps to cleanup the config data in the cases, when the framework has not been stopped gracefully right after a bundle with bound configuration was uninstalled.