Improve log message when bundle start level not valid for start --------------------------------------------------------------- Key: JBOSGI-625 URL: https://issues.jboss.org/browse/JBOSGI-625 Project: JBoss OSGi Issue Type: Bug Security Level: Public(Everyone can see) Components: Core Framework Affects Versions: JBossOSGi 1.1.1 Environment: Jboss as 7.1.2.Final JDK6 EAP 6.0.0 Reporter: Daniel Chapman Assignee: Thomas Diesler Priority: Minor Fix For: JBossOSGi 1.2.0 When I set org.jboss.osgi.framework to DEBUG, I get messages like the following: 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Starting bundle: org.apache.aries.blueprint:1.0.0 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Start level [2] not valid for: org.apache.aries.blueprint:1.0.0 I'd like more information on this message. I've seen it during various startup configurations in messing with my capabilities and it seems to matter little when fixing real issue. What I'm doing above is clicking the Start Bundle button in the osgi console. It prints these two messages as DEBUG, nothing else is printed, and net result is console refreshes and no changes have been made to the status of the bundle. So is this message really relevant, if so - then why DEBUG only. Second - what do I do when I got to start a module, nothing is printed to logs (except above) and the bundle doesn't actually start? Thanks!