OSGI Bundle get stopped after hitting url | Community
Skip to main content
T
test566
Level 2
February 10, 2023
Solved

OSGI Bundle get stopped after hitting url

  • February 10, 2023
  • 3 replies
  • 1566 views

Hi All,

Whenever I hit the URL 

http://127.0.0.1:4502/etc/replication/agents.publish.json

My bundle get automatically goes to resolved status from active.

this happened only when i access through ip address .

does any one having same issue.

 

I checked error.log but it is not showing any information.

 

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 joerghoh

I don't think that this call is the reason that any bundle gets non-active. While this is technically possible to do, I have yet to see code, which does that for a reason.

The only exception is the Bundle Disabler by ACS AEM Commons (https://adobe-consulting-services.github.io/acs-aem-commons/features/osgi-disablers/bundle-disabler/index.html), but if you configure that one, it will immediate deactivate a bundle as soon as you have activated it.

Please check the logs to get a better impression of the timing, because if a bundle is deactivated you should see a log message.

3 replies

Ritesh_Mittal
Community Advisor and Adobe Champion
Ritesh_MittalCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
February 10, 2023

Hi @test566 ,

 

Which bundle is going to resolved state? Do you have any custom servlet/service in your system which uses/invokes replication agent programmatically.

 

Thanks,

Ritesh Mittal

    T
    test566Author
    Level 2
    February 10, 2023

    Hi @ritesh_mittal ,

    Project core bundle

    we have 40+ custom servlet having 

    resourceTypes = NameConstants.NT_PAGE

    but  no servlet  which handled replication agent .

      Ritesh_Mittal
      Community Advisor and Adobe Champion
      Ritesh_MittalCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      February 10, 2023

      Hi @test566 ,

       

      Just try to stop/start the bundle and watch the logs while starting.

       

      Thanks,

      Ritesh Mittal

        Jagadeesh_Prakash
        Community Advisor
        Jagadeesh_PrakashCommunity Advisor
        Community Advisor
        February 10, 2023

        @test566 I tried this in my local instance and its working fine. Issue could be from your project code. Once try on vineela instance. 

         

        But point to worry is "this happened only when i access through ip address ." I am not sure how is this happening only on ip address.

          joerghoh
          Adobe Employee
          joerghohAdobe EmployeeAccepted solution
          Adobe Employee
          February 11, 2023

          I don't think that this call is the reason that any bundle gets non-active. While this is technically possible to do, I have yet to see code, which does that for a reason.

          The only exception is the Bundle Disabler by ACS AEM Commons (https://adobe-consulting-services.github.io/acs-aem-commons/features/osgi-disablers/bundle-disabler/index.html), but if you configure that one, it will immediate deactivate a bundle as soon as you have activated it.

          Please check the logs to get a better impression of the timing, because if a bundle is deactivated you should see a log message.

            Terms & ConditionsAccessibility statement

            Loading footer...