Problem with code bundle component on instance restarts, but the component works when package imports are refreshed or code is redeployed | Community
Skip to main content
this-that-the-otter
this-that-the-otter
Level 4
November 30, 2022
Solved

Problem with code bundle component on instance restarts, but the component works when package imports are refreshed or code is redeployed

  • November 30, 2022
  • 1 reply
  • 1552 views

AEM 6.5 SP13

We have a code bundle with a search component that is in a failed state when the instance is restarted.

Looking around /system/console we see what looks like a conflict with jersey client / jersey core libraries when it's broken (i.e. after instance is restarted).

So far, I have discovered 2 scenarios that seem to fix the issue once the instance has been restarted and the search is broken:

1) If we redeploy the code with mvn clean install -P deploy profile, the search component is fixed

2) If within the /system/console I select the "refresh package imports" button for this bundle, the problem also almost always resolves

Is it possible to refresh package imports for a bundle via cURL?

I imagine the number of the bundle could change making this more difficult that it might already be.

Thanks for any help!

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 SantoshSai

Hi @this-that-the-otter ,

IMO, You should not refresh bundle either manually or via any command. Ideally you may resolve it on your lower environment but when it comes to production and/or pre-production console is inaccessible. I would find out the root cause and fix it. Please check with the bundle version. for more details refer these articles and similar thread: 

Regards,

Santosh

1 reply

Avinash_Gupta_
Community Advisor and Adobe Champion
Avinash_Gupta_Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
November 30, 2022

Hi @this-that-the-otter 

 

You can refresh the entire bundle using the below CURL command:-

 

curl -u admin:admin -F action=refresh http://localhost:4502/system/console/bundles/$bundle symbolic name 

    this-that-the-otter
    this-that-the-otterAuthor
    Level 4
    November 30, 2022

    Hi Avinash,

    Thank you for the info, it seems to work! Interestingly, Adobe Support said you could not refresh a bundle like this via cURL 🙂

    Do you have any idea why this is necessary in our case? Ideally the code would come back properly between restarts of the AEM instance. This will make things easier though, definitely faster than logging into /system/console and manually refreshing, or redeploying the code.

    I issued the command and saw a lot of things scroll by in error.log so it seemed to work well, the command returned the following:

    {"fragment":false,"stateRaw":32}⏎

    Thanks again!

      SantoshSai
      Community Advisor
      SantoshSaiCommunity AdvisorAccepted solution
      Community Advisor
      November 30, 2022

      Hi @this-that-the-otter ,

      IMO, You should not refresh bundle either manually or via any command. Ideally you may resolve it on your lower environment but when it comes to production and/or pre-production console is inaccessible. I would find out the root cause and fix it. Please check with the bundle version. for more details refer these articles and similar thread: 

      Regards,

      Santosh

      Santosh Sai
        Terms & ConditionsAccessibility statement

        Loading footer...