You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Ralf Steppacher (JIRA)" <ji...@apache.org> on 2016/01/12 09:09:39 UTC

[jira] [Commented] (KARAF-4261) Bundle start-level seems to be ignored at Karaf restart

    [ https://issues.apache.org/jira/browse/KARAF-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093503#comment-15093503 ] 

Ralf Steppacher commented on KARAF-4261:
----------------------------------------

It looks like the bundle start-level is also not fully honored during the initial KAR deployment either. Or my understanding of the start-level is wrong.

I have changed the order in which my bundles should be started such that my data access bundle starts before the webservices start and shuts down after the webservices have shut down. However, the change is not reflected in the start/stop order of the bundles. The data access bundle (_Graph Manager_, id 206) is still consistently started last and shut down first. Though looking at the start-levels it should be the other way round:

{noformat}
karaf@root()> bundle:list | grep 4.0.3.SNAP
 52 | Active      |  88 | 4.0.3.SNAPSHOT | Base
 60 | Active      |  89 | 4.0.3.SNAPSHOT | Patient webservice implementation
 63 | Active      |  89 | 4.0.3.SNAPSHOT | Camel UnboundIDLDAP Component
 65 | Active      |  91 | 4.0.3.SNAPSHOT | Webservice Health Professionals
152 | Active      |  91 | 4.0.3.SNAPSHOT | REST API
167 | Active      |  91 | 4.0.3.SNAPSHOT | Webservice Patients
168 | Active      |  91 | 4.0.3.SNAPSHOT | Webservice Patient Registration
177 | Active      |  91 | 4.0.3.SNAPSHOT | PEP
206 | Active      |  90 | 4.0.3.SNAPSHOT | Graph Manager
karaf@root()>
{noformat}

> 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
>    Affects Versions: 4.0.3
>            Reporter: Ralf Steppacher
>
> 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.3.4#6332)