Why doesn't an OSGi Bundle start even when all the Dependencies are resolved? | Community
Skip to main content
khamat_bn
khamat_bn
Level 4
October 11, 2019
Solved

Why doesn't an OSGi Bundle start even when all the Dependencies are resolved?

  • October 11, 2019
  • 6 replies
  • 5042 views

I have installed bundle, all the dependencies got resolved also but it didnt go to Active State. Why?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

The prerequisite of OSGI components being started is that the bundle is active. But not the other way around (a bundle might be active and none of its containing components is started).

6 replies

S
Adobe Employee
sdangAdobe Employee
Adobe Employee
October 11, 2019

There could be any number of reasons why this is happening. Could you post the fragment of the error log showing what happens when you manually try to start the bundle?

    H
    Adobe Employee
    Hamid1350Adobe Employee
    Adobe Employee
    October 11, 2019

    Check package dependencies to make sure there is nothing missing:

    http://localhost:4565/system/console/depfinder

      Ankur_Khare
      Community Advisor
      Ankur_KhareCommunity Advisor
      Community Advisor
      October 12, 2019

      Could u pls post error.log when u upload the jar file to system console

        joerghoh
        Adobe Employee
        joerghohAdobe Employee
        Adobe Employee
        October 13, 2019

        If all dependencies of a bundle are resolved, but it does not go into active state, then there I see 2 possibilities:

        * This bundle has a bundle activator configured, which throws an exception.

        * You use the Bundle Disabler of ACS AEM Commons, which disables this bundle as soon it gets activated.

          rampai
          Community Advisor
          rampaiCommunity Advisor
          Community Advisor
          October 13, 2019

          Probably an OSGi component that you have in your bundle is in unsatisfied state.

            joerghoh
            Adobe Employee
            joerghohAdobe EmployeeAccepted solution
            Adobe Employee
            October 13, 2019

            The prerequisite of OSGI components being started is that the bundle is active. But not the other way around (a bundle might be active and none of its containing components is started).

              Terms & ConditionsAccessibility statement

              Loading footer...