OSGI component changed to satisfied state | Community
Skip to main content
S
SrikanthPo3
Level 5
December 5, 2023

OSGI component changed to satisfied state

  • December 5, 2023
  • 2 replies
  • 773 views

Hi,

One of our custom OSGI component went into satisfied state from active state in AEM production publisher instances(3 publishers) which resulted in a broken functionality on production site. We had to manually bring the component back to active state. There was no deployment activities on that particular day, the particular component was active before the issue occurred. Anyone has idea what might be the reason for certain component going into satisfied state from active?

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

2 replies

Sudheer_Sundalam
Community Advisor
Sudheer_SundalamCommunity Advisor
Community Advisor
December 5, 2023

@srikanthpo3 ,

I have not seen any component or bundle turning into satisfied state from active without any external interference meaning machine restart, AEM restart, deployments or some other dependency bundle restarts.

Inspecting the logs from that day can give some more insight of what might have happened.

    S
    SrikanthPo3Author
    Level 5
    December 5, 2023

    Hi @sudheer_sundalam , thanks for the inputs, will check with AMS team to see if there was activity done by them and also check the logs to find the root cause.

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      January 2, 2024

      @srikanthpo3 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...