Bundle bluepring-syslog-handler-default cannot be started and blocks Karaf container completly
Description
In some circumstances it may occur, that the Karaf Container does not initialize completely.
In that case the bundle "org.opennms.features.events.syslog.blueprint-syslog-handler-default" is starting and hangs in state "Creating".
The bundle is not continuing starting up and blocks the whole startup process of karaf. Looking at the karaf log, it seems, that the activemq broker is not started:
Looking in the eventd.log, this seems to true:
I also set a breakpoint in the BrokerFactoryBean#afterPropertiesSet to see if the broker is initialized, but that method id never invoked. Looking again at the eventd.log it seems, that the `applicationContext-activemq.xml` is started AFTER the `applicationContext-common` which may cause the problem.
We should make sure, that the broker is always initialized first.
Because starting bundle blocks karaf completely. It is not possible to start/stop/uninstall that bundle. Stopping OpenNMS is also not possible. We should make sure, that bundles do not block the startup of karaf if the broker is not available (yet).
Not sure if that is related, but I run into the issue that a Minion had a JMX datacollection outage after restarting ONMS. I'm running on 24.1.0 (ONMS and Minion).
Eventd shows:
Jesse White January 10, 2017 at 10:49 AM
The changes have been merged, the features in question no longer exist.
Jesse White January 9, 2017 at 11:57 AM
This is caused by the changes in , and will be fixed as part of .
(These features will no longer be used and communication will be done using the vm:// protocol instead of tcp://)
In some circumstances it may occur, that the Karaf Container does not initialize completely.
In that case the bundle "org.opennms.features.events.syslog.blueprint-syslog-handler-default" is starting and hangs in state "Creating".
The bundle is not continuing starting up and blocks the whole startup process of karaf.
Looking at the karaf log, it seems, that the activemq broker is not started:
Looking in the eventd.log, this seems to true:
I also set a breakpoint in the BrokerFactoryBean#afterPropertiesSet to see if the broker is initialized, but that method id never invoked.
Looking again at the eventd.log it seems, that the `applicationContext-activemq.xml` is started AFTER the `applicationContext-common` which may cause the problem.
We should make sure, that the broker is always initialized first.
Because starting bundle blocks karaf completely. It is not possible to start/stop/uninstall that bundle. Stopping OpenNMS is also not possible.
We should make sure, that bundles do not block the startup of karaf if the broker is not available (yet).