Skip to main content
manis70983965
May 28, 2015 6:05 PM UTC
Solved

Issue with unbinding of configurations from old jars

Hi All,

I know that this has been discussed in 2012 via the post - Issue with unbinding of configurations from old jars but even then there was no definite solution to this issue. I am facing the same issue now where my config does not pick up the latest snapshot unless I unbind and save.

If someone has an answer, please do help.

Regards,

Mani

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
aanchal-sikka
aanchal-sikkaAccepted solution
Community Advisor
Apr 24, 2024 5:59 AM UTC

The issue is no longer reproducible in latest versions of AEM. Validated on AEM 6.5

Aanchal Sikka
View in thread

4 replies

garyT
Level 2
May 28, 2015 6:51 PM UTC

Have you checked with Adobe daycare/support on this one? If it is a bug/configuration issue that might be your resolving it.

Translate
    manis70983965Author
    May 29, 2015 4:14 AM UTC

    we did that a year ago.. but I was not on this project then. Adobe wasn't able to come around with a solution for this one then. Will do it again today.

    Translate
      aanchal-sikka
      Community Advisor
      aanchal-sikkaCommunity AdvisorAccepted solution
      Community Advisor
      Apr 24, 2024 5:59 AM UTC

      The issue is no longer reproducible in latest versions of AEM. Validated on AEM 6.5

      Translate
      Aanchal Sikka
        AmitVishwakarma
        Community Advisor
        AmitVishwakarmaCommunity Advisor
        Community Advisor
        Jan 18, 2025 5:32 AM UTC

        Hi @manis70983965 

        To fix the issue where AEM config doesn't pick up the latest snapshot:

        1. Check OSGi Configuration: Ensure the correct configuration is applied in the AEM Web Console (/system/console/configuration).

        2. Clear Bundle Cache: Clear the OSGi bundle cache or restart AEM to force it to reload the latest snapshot.

        3. Verify Bundle Version: Make sure the correct snapshot version is being used and re-deploy the bundle if needed.

        4. Use Sling Resource Resolver: Check if your Sling mappings or resource resolvers are correctly updated.

        5. Unbind and Save Config: Sometimes manually unbinding and saving configurations in the OSGi console is required to apply updates.

        These steps should help resolve the issue.

        Translate
        Amit Vishwakarma - Adobe Commerce Champion 2025 | 17x Adobe certified | 6x Adobe SME
        Terms & ConditionsAccessibility statement

        Loading footer...