karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (KARAF-4261) Bundle start-level seems to be ignored at Karaf restart
Date Wed, 18 Oct 2017 16:41:00 GMT

     [ https://issues.apache.org/jira/browse/KARAF-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Guillaume Nodet closed KARAF-4261.
----------------------------------
       Resolution: Cannot Reproduce
         Assignee: Guillaume Nodet  (was: Jean-Baptiste Onofré)
    Fix Version/s:     (was: 4.1.4)
                       (was: 4.0.11)
                       (was: 4.2.0)

I can't reproduce any problem with start levels.
Here is a simple project:

{code}
karaf@root()> feature:info --xml features
    <feature name="features" description="features" version="1.0.0.SNAPSHOT">
        <bundle start-level="61">mvn:org.example.karaf.startlevel/bundle1/1.0.0-SNAPSHOT</bundle>
        <bundle start-level="60">mvn:org.example.karaf.startlevel/bundle2/1.0.0-SNAPSHOT</bundle>
    </feature>
karaf@root()> feature:install features
Bundle 25/org.example.karaf.startlevel.bundle2 is starting
Bundle 24/org.example.karaf.startlevel.bundle1 is starting
karaf@root()> feature:stop features
Bundle 24/org.example.karaf.startlevel.bundle1 is stopping
Bundle 25/org.example.karaf.startlevel.bundle2 is stopping
karaf@root()> feature:start features                                                  
                                                                                   
Bundle 25/org.example.karaf.startlevel.bundle2 is starting
Bundle 24/org.example.karaf.startlevel.bundle1 is starting
karaf@root()>                                                                         
                                                                                         
                
Bundle 24/org.example.karaf.startlevel.bundle1 is stopping
Bundle 25/org.example.karaf.startlevel.bundle2 is stopping
gnodet•apache-karaf-minimal/target/assembly(master⚡)» bin/karaf debug               
                                                                                         
      [18:39:06]
Listening for transport dt_socket at address: 5005
        __ __                  ____      
       / //_/____ __________ _/ __/      
      / ,<  / __ `/ ___/ __ `/ /_        
     / /| |/ /_/ / /  / /_/ / __/        
    /_/ |_|\__,_/_/   \__,_/_/         

  Apache Karaf (4.2.0-SNAPSHOT)

Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf.

Bundle 25/org.example.karaf.startlevel.bundle2 is starting
Bundle 24/org.example.karaf.startlevel.bundle1 is starting
karaf@root()>                                                                         
                                                                                         
                
Bundle 24/org.example.karaf.startlevel.bundle1 is stopping
Bundle 25/org.example.karaf.startlevel.bundle2 is stopping
{code}

> Bundle start-level seems to be ignored at Karaf restart
> -------------------------------------------------------
>
>                 Key: KARAF-4261
>                 URL: https://issues.apache.org/jira/browse/KARAF-4261
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core, karaf-kar
>    Affects Versions: 4.0.3
>            Reporter: Ralf Steppacher
>            Assignee: Guillaume Nodet
>
> AS a workaround for CAMEL-9483 I have set a start-level for my bundles deployed as part
of my features. This works as expected during initial deployment (order of deployment is according
to the start levels I set), but not during sub-sequent starts of Karaf. It appears the start-level
of the bundles is ignored, meaning the order of deployment of my bundles is more or less random
and I observe the issues described in CAMEL-9483 again.
> {{bundle:list}} shows my bundles with the start-levels they have been originally deployed
with, though.
> As a workaround I set {{karaf.clean.all = true}} in system.properties.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message