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

Avatar

Avatar

khamat_bn

Avatar

khamat_bn

khamat_bn

11-10-2019

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

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.1K

Likes

1.1K

Correct Reply

1.1K

Avatar

Jörg_Hoh

Employee

Total Posts

3.1K

Likes

1.1K

Correct Reply

1.1K
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)

Avatar

Avatar

rampai

Avatar

rampai

rampai

13-10-2019

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

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.1K

Likes

1.1K

Correct Reply

1.1K

Avatar

Jörg_Hoh

Employee

Total Posts

3.1K

Likes

1.1K

Correct Reply

1.1K
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.

Avatar

Avatar

Ankur_Khare

MVP

Avatar

Ankur_Khare

MVP

Ankur_Khare
MVP

11-10-2019

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

Avatar

Avatar

hamidk92094312

Employee

Avatar

hamidk92094312

Employee

hamidk92094312
Employee

11-10-2019

Check package dependencies to make sure there is nothing missing:

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

Avatar

Avatar

SonDang

Employee

Avatar

SonDang

Employee

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?