/tmp/mydump Diagnostic dump created. DIAGNOSTIC It's not always easy for the developers to understand why a bundle is not active. It could be because the Activator failed, the Blueprint container start failed test container removes all test runner folders. If you want to keep them for any reasons (e.g. check why a test fails) set the following option: @Configuration public Option[] config() { return new Option[]{

classes/resources contained in the bundle bundle:diag Displays diagnostic information why a bundle is not Active bundle:dynamic-import Enables/disables dynamic-import for a given dataSource=scheduler org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.StdJDBCDelegate That’s why this default configuration may appear like "small". By default, Apache Karaf uses: • -Xms128M • -d ( -- directory ) option: 5.1.2. Diagnostic It’s not always easy for developers to understand why a bundle is not active. It could be because the Activator failed, the Blueprint container start failed

a database/shared filesystem as a shared resource and polling instead of multicasting events. So why use Hazelcast ? Hazelcast fits in perfectly because it offers: • Auto discovery ◦ Cluster nodes

a database/shared filesystem as a shared resource and polling instead of multicasting events. So why use Hazelcast ? Hazelcast fits in perfectly because it offers: • Auto discovery ◦ Cluster nodes