Aled Sage created BROOKLYN-608:
----------------------------------
Summary: karaf startup: javax.annotation-api stopped + restarted
(can cause startup to fail)
Key: BROOKLYN-608
URL: https://issues.apache.org/jira/browse/BROOKLYN-608
Project: Brooklyn
Issue Type: Bug
Reporter: Aled Sage
When starting Brooklyn karaf 1.0.0-SNAPSHOT, we see in the log that
\{{javax.annotation-api/1.2.0}} is started and then stopped again (to be
replaced with v1.3)
{noformat}
2019-01-25T10:10:40,561 - INFO 11 o.a.k.f.i.s.FeaturesServiceImpl
[tures-3-thread-1] Stopping bundles:
2019-01-25T10:10:40,562 - INFO 11 o.a.k.f.i.s.FeaturesServiceImpl
[tures-3-thread-1] javax.annotation-api/1.2.0
2019-01-25T10:10:40,563 - INFO 11 o.a.k.f.i.s.FeaturesServiceImpl
[tures-3-thread-1] org.ops4j.pax.logging.pax-logging-log4j2/1.10.1{noformat}
This causes many other bundles to be reloaded. In Brooklyn, this takes a few
seconds. But in downstream projects that embed or build on Brooklyn, the
consequence can be much worse - unloading javax.annotation-api causes so many
bundles to be stopped that Karaf really struggles to figure out the
dependencies - CPU usage maxes out for several minutes, and then it seemingly
hangs (cpu goes to zero, and nothing else appears in the logs).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
