Uploaded image for project: 'Karaf'
  1. Karaf
  2. KARAF-2338

Felix File Install property (felix.fileinstall.active.level) is not working

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: 2.2.9, 2.3.0
    • Fix Version/s: None
    • Component/s: karaf-core
    • Labels:
      None

      Description

      We are having 3 bundles and we want to deploy bundle1 and bundle 2 as part of boot feature and bundle 3 via file install(deploy folder).
      We want to maintain the deployment order in such a way that bundle as part of boot feature deployed first and then bundle from deploy folder is deployed.
      For example:
      1st)Bundle2
      2nd)Bundle1
      3rd)Bundle3

      In order to maintain this behavior we have set the following property in org.apache.felix.fileinstall-deploy.cfg

      felix.fileinstall.active.level =84

      This level is way higher than the Bundle1(Level:75) & Bundle2(Level:60) level

      But we are not able to achieve the required behavior after launching the karaf with clean cache.

      The bundles are getting deployed in the following order.
      1)Bundle2
      2)Bundle3
      3)Bundle1

      When I restart the karaf(without cleaning cache) then bundles are getting deployed in the right order.
      1)Bundle2
      2)Bundle1
      3)Bundle3

      It look like that "felix.fileinstall.active.level" is not applied properly.

        Attachments

        1. Bundle3-0.0.1-SNAPSHOT.jar
          4 kB
          Shrish Srivastava
        2. org.apache.felix.fileinstall-deploy.cfg
          1 kB
          Shrish Srivastava
        3. try.zip
          7 kB
          Shrish Srivastava

          Issue Links

            Activity

              People

              • Assignee:
                jbonofre Jean-Baptiste Onofré
                Reporter:
                shrishs Shrish Srivastava
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: