How to find conflicts when getting “OakState0001” error in AEM
If you encounter the OakState0001 error in the Adobe Experience Manager, please refer to the steps outlined in this article to identify any conflicts.
Description description
Environment
-
Adobe Experience Manager 6.x
-
Adobe Experience Manager as a Cloud Service
Issue/Symptoms
How to find conflicts when getting OakState0001 error in AEM
Conflicts can occur when multiple sessions concurrently update the same content.
For example:
Two sessions started concurrently for the same contents as below:
In that case, Session A got error OakState0001
Session A started at 01:00
Session B started at 01:05
Session B finished at 01:10 => complete with success
Session A finished at 01:15 => got error OakState0001
Resolution resolution
To find conflicts in AEM, follow the steps below:
-
Search OakState0001: Unresolved conflicts in in error.log.
-
Identify the time of the error occurrence and which contents were conflicted.
Example:
When opening a page of /content/wcm/sites/www/mysite/en/jcr:content/pagepar/mainpar.html,
/content/wcm/sites/www/mysite/en/jcr:content/pagepar/mainpar/common_button was conflicted.
code language-none 23.03.2017 11:36:08.734 *ERROR* [ 10.16.146.54 [ 1490236567948] GET /content/wcm/sites/www/mysite/en/jcr:content/pagepar/mainpar.html HTTP/1.1] jp.co.g.aem.util.NodeUtils Error setProperty javax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts in /content/wcm/sites/www/mysite/en/jcr:content/pagepar/mainpar/common_button
Cause:
In most cases, the following might be the root cause:
-
The same operation was triggered in a short time.
-
Customized workflow or JSP being used without consideration of session management.