Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

javax.jcr.InvalidItemStateException: OakState0001|com.day.cq.wcm.core.impl.servlets.ThumbnailServlet Error while adding thumbnail.

Avatar

Level 4

Hi Team,

Getting below error 

Coming from 07.06.2021 09:06:42.963 *ERROR* [10.43.0.52 [1623020802547] GET /content/test/lists/spacing-bottom-desktop.thumb.48.48.png HTTP/1.1] com.day.cq.wcm.core.impl.servlets.ThumbnailServlet Error while adding thumbnail.
javax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts in /apps/test/templates/genericlist/thumbnail.png/jcr:content/dam:thumbnails/dam:thumbnail_48.png/jcr:content
 at org.apache.jackrabbit.oak.api.CommitFailedException.asRepositoryException(CommitFailedException.java:238)
Caused by: org.apache.jackrabbit.oak.api.CommitFailedException: OakState0001: Unresolved conflicts in /apps/test/templates/genericlist/thumbnail.png/jcr:content/dam:thumbnails/dam:thumbnail_48.png/jcr:content

 

it looks when page is created using template thumbnail image rendition gets updated. Also could see mixinType:damThumbnails set on jcr:content node of thumbnail.png of specific template set.

 

Any specfic cause of error r anyone has faced similar issue.

1 Accepted Solution

Avatar

Correct answer by
Employee

Hello @NehaCMS ,

 

This is a known issue in the product and is tracked internally via CQ-4201612. These messages are harmless.

 

Regards,

Manish Singh

View solution in original post

0 Replies

Avatar

Community Advisor

I am also facing the same issue but I see this issue sometimes(creating page first time), the reason for the exception is concurrent session but not sure why are multiple sessions writing on the same node even in my local system.

https://helpx.adobe.com/in/experience-manager/kb/how-to-find-conflicts-when-getting-oakstate0001.htm...

Avatar

Correct answer by
Employee

Hello @NehaCMS ,

 

This is a known issue in the product and is tracked internally via CQ-4201612. These messages are harmless.

 

Regards,

Manish Singh