Nice one Arun. Thank you for sharing it across.

Hi Manoj,Do you have any jira /daycare ticket number that was provided to you w.r.t this issue.

Ok. Thank you @manojd55574250 for letting us know on this.

Hi Hamid,- We do not suspect any issues with user/groups/acls . However, will cross-check on it.- When the same content package[without any custom code deployment] is put onto fresh 6.2 and 6.5 without any user/groups/acls, we see this happening only in 6.5 and NOT in 6.2. That is bit weird.- Also, ...

Hi All,Just an udpate.If we spin up fresh 6.2 and 6.5 instances and put same content package (without deploying any custom code)  in both and hit the url http://localhost:4504/sites.html/content in both the cases. We get errors on 6.5, but not 6.2.This kind of looks like an OOTB issue.Can you please...

Hi hamidk11679710​,We are also facing the same issue on migration to 6.5 from 6.2.Just wanted to check if you have any pointers/thoughts on this.

Hi All,We have set up 6.5 author and publish local machine. On activation of page, for ex: http://localhost:4502/editor.html/content/we-retail/us/en/men.html and checking on publish http://localhost:4503/content/we-retail/us/en/men.html for "Experience" section in footer, we see that "/content" is s...

Hi Joerg,Thank you for the information provided.However, we are not very sure as to how to modify the code to avoid this CM rule check.Arun Patidar​ Adding a finally block didn't help much. Any pointers/ thoughts on how this can be done will be helpful.

Hi Arun,I mean the code in Creating an Event Listener for Adobe Experience Manager 6.4  is working fine but cloud manager is throwing AEM-3[Non-thread safe object used as a field of Servlet/ Filter etc.] while deployment to our servers, which probably we will not be able to fix.So, we were exploring...

Just adding details : The listener implemented is on similar lines as done in Creating an Event Listener for Adobe Experience Manager 6.4.To that implementation,  we are checking if eventIterator.nextEvent().getPath(); has the jcr:title and other properties and based on that we are adding our custom...