Hi Team,
We are frequently getting alerts as concurrently writing to this session alerts.
19.03.2021 19:47:56.215 *WARN* [10.43.0.33 [1616183252926] GET /content/ingredion/ingredients/na/thermflo-06810107.html HTTP/1.1] org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate Attempted to perform hasProperty while thread 10.43.0.33 [1616183246828] GET /content/ingredion/ingredients/na/globe-24-de-corn-syrupglucose-solids-019240.html HTTP/1.1 was concurrently writing to this session. Blocked until the other thread finished using this session. Please review your code to avoid concurrent use of a session.
Could you please suggest how to avoid or handle this?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @chandramohanred you can get an idea from this post: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/unexpected-concurrency-war...
Thanks,
Bilal.
Hi @chandramohanred
Are you trying to do anything in a loop somewhere in code with "hasProperty" ?
Also can you please provide some more info like which version of AEM and which service pack?
Thanks!
Hi @chandramohanred,
Please check my answer here on how to use sessions, resource resolvers to avoid session leaks.
Hope this helps.
Thanks,
Kiran Vedantam.
Hi @chandramohanred you can get an idea from this post: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/unexpected-concurrency-war...
Thanks,
Bilal.
Go through the beautiful article by @Jörg_Hoh , will be helpful.
https://cqdump.joerghoh.de/2015/03/02/aem-scaling-patterns-avoid-shared-sessions/
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies