sling:OsgiConfig not reflected in Configuration Manager

[selvendranr1864]

Hi Team,

I have created a sling:OsgiConfig node with some properties under /apps/myproject/brand/config/brand.locale.configs as shown below. This is reflected in http://localhost:4502/system/console/configMgr  as well with the same name brand.locale.configs

For the past few days we are noticing where the brand.locale.configs is not reflected in http://localhost:4502/system/console/configMgr.

If we delete the node and installed the code package it started reflecting in http://localhost:4502/system/console/configMgr

Otherwise if we go and change any value in CRX, it got reflected in http://localhost:4502/system/console/configMgr

Not sure how the config went missing in the http://localhost:4502/system/console/configMgr and to correct it, we need to delete the node or change some values in the config in the code and deploy that package.

Need to know, what could be the reason the OSGI config is not registered in http://localhost:4502/system/console/configMgr . Even it is missing, why it is expecting some change or need to delete it and install the package to get the config reflected in http://localhost:4502/system/console/configMgr . Also we are not able to replicate this scenario every time(i.e OSGI config not getting registered)

Also we have some run mode specific configs and filter paths are mutually exclusive. Will this cause any issue? Could you please let me help on this issue.

Thanks,

Selva

[Jörg_Hoh]

Can you check if you have a node in /system/sling/installer/jcr/pauseInstallation? In case yes, delete it. If that does not help: have you already restarted the instance?

Jörg

[selvendranr1864]

Hi Jorg,

Checked even when the issue occurred and the "pauseInstallation" node was empty that time. Now I have restarted the instance and the issue not occurred and not able to reproduce the issue. But my worry is what if the issue occur again in higher environments. Is there anything which I should check if the issue occurs again. ? Please let me know.

[Jörg_Hoh · Accepted solution]

Hi,

if a restart fixed the issue, it's likely a problem with the JCRInstaller, which is supposed to install any config change from the repo into OSGI. If you run AEM 6.4, you have a threaddump per minute, and you can check there if there's a thread named "JcrInstaller.1"; also check your error.log files if you find any messages indicating that you had an issue with the JcrInstaller.

HTH,

Jörg