[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-625) Start level not valid message

[Thomas Diesler (JIRA)]

    [ https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750473#comment-12750473 ] 

Thomas Diesler edited comment on JBOSGI-625 at 1/25/13 4:44 AM:
----------------------------------------------------------------

Daniel, could you perhaps work with me to reproduce this with the latest master? We now have server restart test functionality that should allow us to isolate the issue (outside the the context of infinispan)



{code}
        // If the Framework's current start level is less than this bundle's start level
        if (startLevelValidForStart() == false) {
            LOGGER.debugf("Start level [%d] not valid for: %s", getBundleStartLevel(), this);
            return;
        }
{code}

I can promote this to info and also say what the current framework start level is. If you want to achieve autostart for your capabilities you can assign a start-level attribute
                
      was (Author: thomas.diesler):
    Daniel, could you perhaps work with me to reproduce this with the latest master? We now have server restart test functionality that should allow us to isolate the issue (outside the the context of infinispan)

{code}
        // If the Framework's current start level is less than this bundle's start level
        if (startLevelValidForStart() == false) {
            LOGGER.debugf("Start level [%d] not valid for: %s", getBundleStartLevel(), this);
            return;
        }
{code}

I can promote this to info and also say what the current framework start level is. If you want to achieve autostart for your capabilities you can assign a start-level attribute
                  
> Start level not valid message
> -----------------------------
>
>                 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!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira