Expand my Community achievements bar.

SOLVED

OSGI Config values are not getting updated

Avatar

Level 4

Hello,

 

We are encountering an issue when trying to update the out-of-the-box (OOTB) OSGI config for the workflow. The configuration values are not being updated even though we have kept them under the config node. The values are not updated when accessing /system/console/ConfigMgr.

 

AEM: 6.5.21.0

PID:
com.day.cq.wcm.workflow.impl.WcmWorkflowServiceImpl

 

Name of the config file:
/apps/project/osgiconfig/config/com.day.cq.wcm.workflow.impl.WcmWorkflowServiceImpl.cfg.json

 

Entries in the config:
{
"cq.wcm.workflow.terminate.on.activate":"false",
"maxThreadPoolSize": "100",
"minThreadPoolSize": "5",
"cq.wcm.worklfow.terminate.exclusion.list": [],
"event.filter":"(!(event.application\=*))"
}

 

Also, please note that we are not allowed to update/delete any OOTB config directly in /system/console/ConfigMgr. We only need to update via package deployment.

 

Can someone please help me identify the issue with this configuration?

1 Accepted Solution

Avatar

Correct answer by
Level 6

Hi @test1234567 

 

There could be several reasons for this. The points below may help you debug further:

  1. Incorrect Config Format:
    Misformatted configs can cause issues. Use OSGi Console (http://localhost:4502/system/console/osgi-installer-config-printer) to create the config, then download it from the Config Printer to ensure correct formatting.

  2. Missing Filter.xml Entry:
    Ensure META-INF/vault/filter.xml includes your config paths. Also, verify deployment via crxde, Maven build logs, and Package Manager.

  3. Existing Config in /apps/system/config:
    Just in case, if you manually created a config via OSGi Console, it gets stored in /apps/system/config, overriding new configs. Delete it from crxde to resolve.

Regards,

Ayush

View solution in original post

10 Replies

Avatar

Level 1

I can see a couple of mistakes in the configuration. After correcting that, the config looks like this: 

{
"cq.wcm.workflow.terminate.on.activate":false,
"maxThreadPoolSize": "100",
"minThreadPoolSize": "5",
"cq.wcm.worklfow.terminate.exclusion.list": [],
"event.filter":"(!(event.application=*))"
}

Avatar

Level 4

Thank you for your reply. However, even after making the above corrections, I still do not see the changes.

Avatar

Level 1

That's interesting. I tried this, and it worked for me. Have you verified whether the code is deployed correctly to the AEM instance?

Avatar

Level 4

Yes, it is deployed to the AEM instance but the config is not picked.

Avatar

Community Advisor

Hi @test1234567 

Try deleting the config from webconsole config first then deploy your config.



Arun Patidar

Avatar

Level 1

If you can access CRXDE, verify that your configuration is present in CRXDE. Additionally, check for any other existing configurations in different locations that may take precedence over this one (such as config.author, etc.).

Avatar

Community Advisor

Hi @test1234567 

If you have changed config directly from osgi console then you will find that config at /apps/system folder and delete it.



Arun Patidar

Avatar

Correct answer by
Level 6

Hi @test1234567 

 

There could be several reasons for this. The points below may help you debug further:

  1. Incorrect Config Format:
    Misformatted configs can cause issues. Use OSGi Console (http://localhost:4502/system/console/osgi-installer-config-printer) to create the config, then download it from the Config Printer to ensure correct formatting.

  2. Missing Filter.xml Entry:
    Ensure META-INF/vault/filter.xml includes your config paths. Also, verify deployment via crxde, Maven build logs, and Package Manager.

  3. Existing Config in /apps/system/config:
    Just in case, if you manually created a config via OSGi Console, it gets stored in /apps/system/config, overriding new configs. Delete it from crxde to resolve.

Regards,

Ayush

Avatar

Community Advisor

@test1234567 ,

 

Check the filter.xml file for the project maven module where you have osgiconfig. Make sure you added in the filter.xml

<workspaceFilter version="1.0">
<filter root="/apps/project/osgiconfig/"/>
</workspaceFilter>

Avatar

Administrator

@test1234567 Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!



Kautuk Sahni