Issue with unbinding of configurations from old jars

[manis70983965]

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

[garyT]

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

[manis70983965]

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.

[aanchal-sikka · Accepted solution]

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

[AmitVishwakarma]

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.