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

[khamat_bn]

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

[SonDang]

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?

[hamidk92094312]

Check package dependencies to make sure there is nothing missing:

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

[Ankur_Khare]

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

[Jörg_Hoh]

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]

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

[Jörg_Hoh · Accepted solution]

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).