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

blueprint disable service too soon at shutdown

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.1
    • Fix Version/s: 2.4.0, 3.0.0, 2.3.4
    • Component/s: karaf-osgi
    • Labels:
      None
    • Environment:

      windows/linux/jdk1.7

      Description

      details discussion is here http://karaf.922171.n3.nabble.com/Orderly-shutting-down-services-td4027336.html

      basically, at shutdown, low startlevel service gets removed too early when higher startlevel bundle still need those service at @predestroy time

        Issue Links

          Activity

          Hide
          pieber Andreas Pieber added a comment -

          after reading the referenced thread I would say this is a aries issue which should be noted/created there too?

          Show
          pieber Andreas Pieber added a comment - after reading the referenced thread I would say this is a aries issue which should be noted/created there too?
          Hide
          danttran Dan Tran added a comment -

          Attached is karaf-2189.zip the proposed workaround mentioned in the user mailing list is not working either

          Show
          danttran Dan Tran added a comment - Attached is karaf-2189.zip the proposed workaround mentioned in the user mailing list is not working either
          Hide
          danttran Dan Tran added a comment -
          Show
          danttran Dan Tran added a comment - I also file a bug at https://issues.apache.org/jira/browse/ARIES-1020
          Hide
          danttran Dan Tran added a comment -

          also, the around mentioned in the nable list discussion does not work either

          Show
          danttran Dan Tran added a comment - also, the around mentioned in the nable list discussion does not work either
          Hide
          gnt Guillaume Nodet added a comment -

          We need to upgrade to aries blueprint-core-1.0.2 when it's released to pick up the fix

          Show
          gnt Guillaume Nodet added a comment - We need to upgrade to aries blueprint-core-1.0.2 when it's released to pick up the fix
          Hide
          lichtin Martin Lichtin added a comment -

          I'm continuously confused by the different Aries versions, but isn't Karaf 2.3.1
          already using org.apache.aries.blueprint.core/1.1.0 ?

          Show
          lichtin Martin Lichtin added a comment - I'm continuously confused by the different Aries versions, but isn't Karaf 2.3.1 already using org.apache.aries.blueprint.core/1.1.0 ?
          Hide
          danttran Dan Tran added a comment -

          @Martin, it should be 1.1.1-SNAPSHOT.

          this fixed my issue

          Show
          danttran Dan Tran added a comment - @Martin, it should be 1.1.1-SNAPSHOT. this fixed my issue
          Hide
          gnt Guillaume Nodet added a comment -

          Yes, sorry, I meant 1.1.1, well whatever > 1.1.0 ...

          Show
          gnt Guillaume Nodet added a comment - Yes, sorry, I meant 1.1.1, well whatever > 1.1.0 ...
          Hide
          jgoodyear Jamie goodyear added a comment -

          Bumping out to 2.3.3 as we'll need the next Aries release.

          Show
          jgoodyear Jamie goodyear added a comment - Bumping out to 2.3.3 as we'll need the next Aries release.
          Hide
          danttran Dan Tran added a comment -

          I think karaf 2.3.x already pickup blueprint-core-1.1.1-SNAPSHOT, you will need to revert it back to 1.1.0

          Btw, I quite disappointed that we not able to get aries team to release 1.1.1. I ended up to release it internally and get my custom karaf 2.3.x to pick it up at our build time

          Show
          danttran Dan Tran added a comment - I think karaf 2.3.x already pickup blueprint-core-1.1.1-SNAPSHOT, you will need to revert it back to 1.1.0 Btw, I quite disappointed that we not able to get aries team to release 1.1.1. I ended up to release it internally and get my custom karaf 2.3.x to pick it up at our build time
          Hide
          chris@die-schneider.net Christian Schneider added a comment -

          The upgrade to the new blueprint core should include the fix for this.

          Show
          chris@die-schneider.net Christian Schneider added a comment - The upgrade to the new blueprint core should include the fix for this.
          Hide
          chris@die-schneider.net Christian Schneider added a comment -

          The upgrade to the new blueprint core should include the fix for this.

          Show
          chris@die-schneider.net Christian Schneider added a comment - The upgrade to the new blueprint core should include the fix for this.

            People

            • Assignee:
              chris@die-schneider.net Christian Schneider
              Reporter:
              danttran Dan Tran
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development