Workbench Doesn't Apply XM Changes Due To StackOverflowError In StoreDeploymentWorker Thread
Last updated on JANUARY 26, 2018
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
We noticed that after some time our Workbench stopped to create new generations in either of these cases.
Due to that any changes made in the Experience Manager are not applied on the site after the Experience Manager project is Published.
The 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.
The StackOverflowError happens when we run the custom script promotePreviewToProd which copies our Preview application to the Production application. (the script attached)
The script copies the content using standard IFCR importApplication and IFCR exportApplication commands.
I believe the StackOverflowError (log of the exception is attached) happens when when the IFCR exportApplication creates the application ZIP file, and checks the permissions of all the files stored in the ZIP.
Most likely the problem is related to the huge number of Workspaces stored in the ToolsAndFrameworks application configuration repository, and when IFCR exportApplication tries to store all these Workspaces into
the application ZIP the StackOverflowError happens.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms