18.3. Container-level Locking
Configuring container-level locking
etc/system.propertiesfile on each system in the master/slave setup:
Example 18.7. Container-level Locking Configuration
karaf.lock=true karaf.lock.level=50 karaf.lock.delay=10000
etc/startup.properties, in the format BundleName.jar=level. The core system bundles have levels below 50, where as user bundles have levels greater than 50.
Table 18.1. Bundle Start Levels
|1||A 'cold' standby instance. Core bundles are not loaded into container. Slaves will wait until lock acquired to start server.|
|<50||A 'hot' standby instance. Core bundles are loaded into the container. Slaves will wait until lock acquired to start user level bundles. The console will be accessible for each slave instance at this level.|
|>50||This setting is not recommended as user bundles will be started.|
Avoiding port conflicts
servicemixstart script (or the
karafscript on a child instance) to include the following:
DEFAULT_JAVA_OPTS="-server $DEFAULT_JAVA_OPTS -Dcom.sun.management.jmxremote.port=1100 -Dcom.sun.management.jmxremote.authenticate=false"