Community
Participate
Working Groups
org.eclipse.osgi 3.6.0.v20100512 When stopping a framework instance with the following bundles available I get a log message which is irritating. 2 RESOLVED ch.qos.logback.classic_0.9.19.v20100519-1505 3 RESOLVED ch.qos.logback.core_0.9.19.v20100419-1216 4 RESOLVED ch.qos.logback.slf4j_0.9.19.v20100519-1910 (Master=27) ... 27 RESOLVED org.slf4j.api_1.5.11.v20100519-1910 (Fragments=4) !ENTRY org.eclipse.osgi 2 0 2010-05-25 16:59:40.374 !MESSAGE Info: cycle(s) found while stopping bundles: [[ch.qos.logback.classic,org.slf4j.api,ch.qos.logback.slf4j,ch.qos.logback.core]]. IMHO the log message is irritating because of the following reasons. (A) It does not provide value to users running the framework instance. A developer knows ahead of time that the bundles have cycles. That's intended behavior. An operator (a user) should not be confronted with this detail. It works regardless. (B) The bundle states are "RESOLVED". Therefore, the framework should not make an attempt to stop them.
This is only be logged if in debug mode (using -debug) and it is just a warning. I am not inclined to fix this debug warning message since cycles often do cause other issues and this can be useful when in debug mode.
*** Bug 344750 has been marked as a duplicate of this bug. ***
*** Bug 405249 has been marked as a duplicate of this bug. ***