ExternalizerImpl OSGi Config Not Updating | Community
Skip to main content
stiegjo22
stiegjo22
Level 4
July 31, 2025
Solved

ExternalizerImpl OSGi Config Not Updating

  • July 31, 2025
  • 1 reply
  • 472 views

 

Hi everyone,

I'm running into an issue with updating the com.day.cq.commons.impl.ExternalizerImpl configuration in AEM (local author instance). I’ve created a runmode-specific config file at:

 

/apps/my-site/config.qa.author/com.day.cq.commons.impl.ExternalizerImpl.xml

 

Here’s the content of the XML:

 
 
<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" jcr:primaryType="sling:OsgiConfig" externalizer.jhinvestments="https://qa-my-site.com/"/>

After deploying this, I expected the ExternalizerImpl config to reflect the new domains. However, when I check /system/console/configMgr/com.day.cq.commons.impl.ExternalizerImpl, it still shows the default domains:

Even if I manually delete the config via the OSGi console, it reverts back to these defaults.

I’ve confirmed:

  • The runmodes are correctly set (qa, author)
  • The config is deployed to the correct path
  • The XML is valid and uses the correct externalizer.<domain> format
  • No other conflicting configs exist in other runmode folders (as far as I can tell)

Has anyone encountered this before? Is there something I’m missing in terms of overriding the default Externalizer domains?

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 stiegjo22

I switched to using cfg.json (not xml) and it's working now. 

 

{ "externalizer.domains": [ "my-site https://qa-my-site.com/", ] }

1 reply

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
August 1, 2025

Hi @stiegjo22 

Are you using AEMaaCS or AEM 6.5?

Custom runmode(e.g. qa) are not supported in AEMaaCS.

Arun Patidar
    stiegjo22
    stiegjo22AuthorAccepted solution
    Level 4
    August 1, 2025

    I switched to using cfg.json (not xml) and it's working now. 

     

    { "externalizer.domains": [ "my-site https://qa-my-site.com/", ] }
      Terms & ConditionsAccessibility statement

      Loading footer...