OSGI Bundles not active after code deployment | Community
Skip to main content
November 2, 2022
Solved

OSGI Bundles not active after code deployment

  • November 2, 2022
  • 3 replies
  • 1138 views

I am facing issues intermittently after code deployment to AEM server, bundles are not active(they are in following state installed, resolved etc...), Uber jar version is also matching with the AEM version which i am using, Please suggest how to resolve it.

 

 
 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by malay_dube

Hi @prashanthal 

Try to replicate the same issue in local instance, and please check dependencies to make sure there is nothing missing.
http://localhost:4502/system/console/depfinder

If it's not AEMaaCS then you can directly check it over actual AEM instance. Based on that modify POM and add required dependencies if anything is missing.

3 replies

Community Advisor
November 2, 2022

Hi,

 

please check package dependencies to make sure there is nothing missing:
http://localhost:4502/system/console/depfinder

Could you please check error.log when you upload the jar file to system console

Could you please check the error.log showing what happens when you manually try to start the bundle?

 

 

arunpatidar
Community Advisor
Community Advisor
November 2, 2022

Are you trying in local or actual AEM server.

If it is in local then provide more help size to AEM instance.

Example - https://www.linkedin.com/pulse/ways-start-aem-sumit-srivastava/?trk=public_profile_article_view 

Arun Patidar
November 2, 2022

@arunpatidar I am facing this issue in Actual AEM server, not local server. 

arunpatidar
Community Advisor
Community Advisor
November 2, 2022

check the logs to see what is happening ?

Arun Patidar
malay_dubeAdobe EmployeeAccepted solution
Adobe Employee
November 3, 2022

Hi @prashanthal 

Try to replicate the same issue in local instance, and please check dependencies to make sure there is nothing missing.
http://localhost:4502/system/console/depfinder

If it's not AEMaaCS then you can directly check it over actual AEM instance. Based on that modify POM and add required dependencies if anything is missing.