Level 4

Solved

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

6 replies
5040 views
Translate

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.

joerghohAccepted solution

Employee

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

joerghohAccepted solution

Employee

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

Translate

rampai

Level 1

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

Translate

joerghoh

Employee

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.

Translate

Ankur_Khare

New Participant

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

Translate

H

Hamid1350

Employee

Check package dependencies to make sure there is nothing missing:

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

Translate

S

sdang

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?

Translate

Sign up

Login with SSO

Login to the community

Login with SSO