All users in aem are stored under /home/users. Do you have a property or anything in particular to distinguish users for a specific website? Are you using AEM communities by any chance or its a normal multi tenant instance?

please check with SP 6.4.4.0. If the issue still exists, file a daycare ticket with the package of the rollout config.On the other hand, make sure to follow MSM Best Practices

IMO, AEM doesn’t support containers currently for on-prem instances, could be an option in the future for AMS(Adobe managed services)

Nice workaround Ravi Pampana

Did you try adding the osgi wrapped bundle to your apps install folder (through code package, with the help of filter.xml) and use the maven-bundle-plugin or content-package-maven-plugin. Please refer [0] & [1] option #4[0]cq5 - How to use third party JAR into AEM? - Stack Overflow[1]Adobe CQ/Adobe ...

Long running sessions might also be the cause for such conflicts as mentioned in [0], Please add debug level logs to the package mentioned by Joerg and additionally add debug level logging around the below packages. This will give more details into the conflictorg.apache.jackrabbit.oak.plugins.commi...

Hope this thread helps how to embed dependent jar ?

These warnings are usually generated when there is a parsys included and the parsys is empty without any components added to it. For example in the below code parsys "warning_test", a node warning_test is not created until there is a component added to parsys "warning_test" and hence the warning mes...

To fix this, you can add cq.shared dependency on "/etc/clientlibs/foundation/main" and it will work fine

You could use the CQ object like below:CQ.I18n.getMessage('Key-name');