Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

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

Avatar

Level 4

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

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

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

View solution in original post

6 Replies

Avatar

Employee

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?

Avatar

Community Advisor

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

Avatar

Employee Advisor

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.

Avatar

Level 6

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

Avatar

Correct answer by
Employee Advisor

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