Getting warning while deleting a component from a page.

Avatar

Avatar

Umesh_Thakur

MVP

Avatar

Umesh_Thakur

MVP

Umesh_Thakur
MVP

31-03-2021

Dear Members,

I am facing one issue while deleting a component from a page.

In aem's error log I can see below warning when try to delete an already authored component in it though component get deleted.

Umesh_Thakur_0-1617189374639.png

Some more details:

this stack trace is from my local.

I am not able to reproduce this issue in wknd site on the same local instance.

though I can see this warning in error log but component get deleted with this warning.

 

so I just wanted to check, is there any way we can handle this warning ?

As per this https://github.com/jwadolowski/cookbook-cq/issues/37 it seems to be a bug but still if anyone can provide some input on it.

 

Thanks

Umesh Thakur

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Umesh_Thakur

MVP

Avatar

Umesh_Thakur

MVP

Umesh_Thakur
MVP

31-03-2021

Thanks everyone for spending sometime for the below issue.

Now we have the root cause of the below warning that is :

We have one org.apache.sling.rewriter.Transformer and org.apache.sling.rewriter.TransformerFactory implementation in our project that was looking for the path, which was deleted as part of the deletion activity, and trying to do some operation.

 

Answers (3)

Answers (3)

Avatar

Avatar

Bhuwan_B

Avatar

Bhuwan_B

Bhuwan_B

31-03-2021

@Umesh_Thakur Can you please check below article and try checking mentioned root cause to fix your issue if that helps.

https://stackoverflow.com/questions/38878394/javax-jcr-invaliditemstateexception-item-cannot-be-save...

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

In most cases, the following might be root cause:

  • Same operation was trigerred in a short time. 
  • Customized workflow or jsp being used wiithout consideration of session management

 

Avatar

Avatar

jbrar

Employee

Avatar

jbrar

Employee

jbrar
Employee

31-03-2021

If the issue is not reproducible on the WKND site, I highly doubt it's an issue with the core AEM code and the issue might be related to the Sling model Or other backend custom code that gets invoked during the component deletion.

 

That said, If you are able to reproduce it without any custom code, I would recommend logging a support case.

 

 

Avatar

Avatar

asutosh_j3

Avatar

asutosh_j3

asutosh_j3

31-03-2021

Hi @Umesh_Thakur 

 

This issue occurs when two threads concurrently try to write or perform same operation to the same location.

Is this reproducible for all the components or for any specific component? Also is this on all the pages or on any specific page?

 

Thanks!