Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 314289

Summary:	Irritating log message "cycle(s) found while stopping bundles"
Product:	[Eclipse Project] Equinox	Reporter:	Gunnar Wagenknecht <gunnar>
Component:	Framework	Assignee:	equinox.framework-inbox <equinox.framework-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, markus.kell.r, markus.tiede, tjwatson
Version:	3.6
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Gunnar Wagenknecht

2010-05-25 11:06:54 EDT

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.

Comment 1 Thomas Watson

2010-06-01 13:12:20 EDT

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.

Comment 2 Gunnar Wagenknecht

2011-05-04 15:25:02 EDT

*** Bug 344750 has been marked as a duplicate of this bug. ***

Comment 3 Thomas Watson

2013-04-09 08:44:54 EDT

*** Bug 405249 has been marked as a duplicate of this bug. ***