Workbench Doesn't Apply XM Changes Due To StackOverflowError In StoreDeploymentWorker Thread
(Doc ID 2353066.1)
Last updated on FEBRUARY 05, 2020
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 11.2 and later
Information in this document applies to any platform.
Workbench doesn't apply XM changes due to
When any rule is Updated and Saved in the Workbench Experience Manager it is supposed to create a new generation file under
The new generation must also be created after promote_content.sh is triggered
Additionally, after some time our Workbench stopped to create new generations in either of these cases.
Due to that behavior any changes made in the Experience Manager are not applied on the site after the Experience Manager project is Published.
Analysis revealed that the issue happened due to StackOverflowError, which happens in the StoreDeploymentWorker daemon thread of the Sling.
After the error the StoreDeploymentWorker can't recover and due to that it doesn't apply the Experience Manager changes.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document