AEM WKND SPA - 503 | Community
Skip to main content
jeremy_trpka-pe
jeremy_trpka-pe
Level 2
June 10, 2021
Solved

AEM WKND SPA - 503

  • June 10, 2021
  • 3 replies
  • 3039 views

Hello,

I wanted to try the WKND SPA Tutorial, and running AEM off of the following:

  • Java 8
  • AEM 6.5.5
  • Maven 6.3.6
  • Archetype 27

I started off with a clean author instance with the service pack installed, and when I first perform the mvn clean install -PautoInstallSinglePackage it would build fine, until...

I turn off the AEM instance and then turn it back on, and then I get the following:

 

HTTP ERROR 503 AuthenticationSupport service missing. Cannot authenticate request. URI: / STATUS: 503 MESSAGE: AuthenticationSupport service missing. Cannot authenticate request. SERVLET: org.apache.felix.http.base.internal.dispatch.DispatcherServlet-6aacc3

 

EDITED 2021-06-11

I did find this error in the logs:

 

10.06.2021 14:48:18.089 *ERROR* [FelixDispatchQueue] aem-guides-wknd-spa.react.core FrameworkEvent ERROR (org.osgi.framework.BundleException: Unable to resolve aem-guides-wknd-spa.react.core [596](R 596.0): missing requirement [aem-guides-wknd-spa.react.core [596](R 596.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.wcm.api)(version>=1.29.0)(!(version>=2.0.0))) Unresolved requirements: [[aem-guides-wknd-spa.react.core [596](R 596.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.wcm.api)(version>=1.29.0)(!(version>=2.0.0)))]) org.osgi.framework.BundleException: Unable to resolve aem-guides-wknd-spa.react.core [596](R 596.0): missing requirement [aem-guides-wknd-spa.react.core [596](R 596.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.wcm.api)(version>=1.29.0)(!(version>=2.0.0))) Unresolved requirements: [[aem-guides-wknd-spa.react.core [596](R 596.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.wcm.api)(version>=1.29.0)(!(version>=2.0.0)))] at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368) at org.apache.felix.framework.Felix.startBundle(Felix.java:2281) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1539) at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308) at java.base/java.lang.Thread.run(Thread.java:834)

 

When I tried to install com.day.cq.wcm.api package directly in the root pom file it will not install let alone fix the situation.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Asutosh_Jena_

Hi @jeremy_trpka-pe 

 

Please upgrade the AEM service pack to 6.5.8.0 and validate. You should not be getting these issue any more.

Also it's preferred to run AEM 6.5 with JDK 11.

https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/development/set-up-a-local-aem-development-environment.html?lang=en

 

Thanks!

3 replies

ibishika
ibishika
Level 4
June 10, 2021

Java 11 is the recommended version for AEM 6.5. Also I would suggest you to give some time to the instance to come up and after that if it does not work, check the logs for error.

    jeremy_trpka-pe
    jeremy_trpka-peAuthor
    Level 2
    June 10, 2021
    I originally tried it with Java 11, and it gave me the same results.
    Asutosh_Jena_
    Community Advisor
    Asutosh_Jena_Community AdvisorAccepted solution
    Community Advisor
    June 11, 2021

    Hi @jeremy_trpka-pe 

     

    Please upgrade the AEM service pack to 6.5.8.0 and validate. You should not be getting these issue any more.

    Also it's preferred to run AEM 6.5 with JDK 11.

    https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/development/set-up-a-local-aem-development-environment.html?lang=en

     

    Thanks!

      jeremy_trpka-pe
      jeremy_trpka-peAuthor
      Level 2
      June 11, 2021
      Right now, our company only has access to the 6.5.5 service pack so updating it to 6.5.8 may not be a viable solution.
      Vijayalakshmi_S
      Vijayalakshmi_S
      Level 10
      June 11, 2021

      Hi @jeremy_trpka-pe,

      Please check the error.log file completely including the rotated error.log files with previous dates (continue till you notice a file without any Error level) to arrive at the original cause. 

      "503 AuthenticationSupport service missing" error has quite a few related reasons to it, hence the need for digging completely. 

      Update this thread with the same if possible. 

        jeremy_trpka-pe
        jeremy_trpka-peAuthor
        Level 2
        June 11, 2021
        I updated my question with something I found in the error logs.
        Terms & ConditionsAccessibility statement

        Loading footer...