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

Accepted Solutions (1)

Accepted Solutions (1)

Jörg_Hoh

Employee

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

Answers (5)

Answers (5)

Jörg_Hoh

Employee

13-10-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.

SonDang

Employee

11-10-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?