Our pom was pointing to the correct 6.3 uber-jar and we have been using ACS Commons 3.9.0.The exception above started appearing randomly in our AEM 6.3 environment. Everything was working since July.We resorted to restoring from a previous backup after confirming the issue wasn't related to content ...