Unable to launch AEM 6.5.0 on MacOS BigSur | Community
Skip to main content
New Participant
Nov 18, 2020 10:32 PM UTC
Solved

Unable to launch AEM 6.5.0 on MacOS BigSur

Unable to start AEM after macOS BigSur update, tried installing fresh version of 6.5.0 and seeing this error.

18.11.2020 14:28:55.547 *ERROR* [Apache Sling Repository Startup Thread] com.adobe.granite.repository.impl.SlingRepositoryManager start: Uncaught Throwable trying to access Repository, calling stopRepository()
java.lang.NoClassDefFoundError: java/security/acl/Group
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.defineClass(BundleWiringImpl.java:2344)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.defineClassParallel(BundleWiringImpl.java:2162)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2096)
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1565)
at org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1982)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
at org.apache.felix.framework.BundleWiringImpl.getClassByDelegation(BundleWiringImpl.java:1375)
at org.apache.felix.framework.BundleWiringImpl.searchImports(BundleWiringImpl.java:1618)
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1548)
at org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1982)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
at com.adobe.granite.repository.impl.SlingRepositoryManager.setupPolicy(SlingRepositoryManager.java:644) [com.adobe.granite.repository:1.6.28]
at com.adobe.granite.repository.impl.SlingRepositoryManager.setupPermissions(SlingRepositoryManager.java:607) [com.adobe.granite.repository:1.6.28]
at com.adobe.granite.repository.impl.SlingRepositoryManager.createRepository(SlingRepositoryManager.java:444) [com.adobe.granite.repository:1.6.28]
at com.adobe.granite.repository.impl.SlingRepositoryManager.acquireRepository(SlingRepositoryManager.java:284) [com.adobe.granite.repository:1.6.28]
at org.apache.sling.jcr.base.AbstractSlingRepositoryManager.initializeAndRegisterRepositoryService(AbstractSlingRepositoryManager.java:471) [org.apache.sling.jcr.base:3.0.4]
at org.apache.sling.jcr.base.AbstractSlingRepositoryManager.access$300(AbstractSlingRepositoryManager.java:85) [org.apache.sling.jcr.base:3.0.4]
at org.apache.sling.jcr.base.AbstractSlingRepositoryManager$4.run(AbstractSlingRepositoryManager.java:455) [org.apache.sling.jcr.base:3.0.4]
Caused by: java.lang.ClassNotFoundException: java.security.acl.Group
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:435)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:589)
at org.apache.sling.launchpad.base.shared.LauncherClassLoader.loadClass(LauncherClassLoader.java:160)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1475)
at org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1982)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
RHarikr2Accepted solution
New Participant
Feb 14, 2022 7:02 PM UTC

The issue was resolved after setting Java home configurations. Looks like the update changed some Java configurations. 

2 replies

RHarikr2AuthorAccepted solution
New Participant
Feb 14, 2022 7:02 PM UTC

The issue was resolved after setting Java home configurations. Looks like the update changed some Java configurations. 

Translate
arunpatidar
New Participant
Feb 17, 2021 8:51 PM UTC

hi,

I am using the latest Mac OS  and AEM 6.3,6.4 and 6.5 works fine.

can you try with vanilla setup?

could be an issue with the existing setup.

Translate
Arun Patidar