Skip to main content
Aaron_Dempwolff
Level 4
Feb 13, 2025 9:10 PM UTC
Solved

Problems with trying to enter the author mode of a page on localhost

Hi, what happens is that I upgraded my AEM instance, I upgraded the following things:

JDK: Oracle JDK 21.0.6

SDK: AEM SDK v2025.1.19149.20250116T154450Z-250100

I got these files from the official Adobe website: https://experience.adobe.com/#/downloads/content/software-distribution/en/general.html

When I finished the installation and I wanted to edit a page I get the following error:

/libs/fd/fd/af/authoring/editors/rendercondition/template/template.jsp(31,0) The absolute uri: http://www.adobe.com/taglibs/guides/2.0 cannot be resolved in either web.xml or the jar files deployed with this application

I think it's a dependency problem in the pom.xml since I used to use JDK 11 and the 2024 SDK before this new versions

What can I do to fix it?

aanchal-sikka
aanchal-sikkaAccepted solution
Community Advisor
Feb 14, 2025 9:11 AM UTC

Adobe documentation suggests

 

The AEM Cloud Service SDK is compatible with Java 21 and can be used to validate the compatibility of your project with Java 21 before executing a Cloud Manager pipeline.

  • Edit a runtime parameter:
    When running AEM locally with Java 21, the start scripts (crx-quickstart/bin/start or crx-quickstart/bin/start.bat) fail due to the MaxPermSize parameter. As a remedy, either remove -XX:MaxPermSize=256M from the script or define the environment variable CQ_JVM_OPTS, setting it to -Xmx1024m -Djava.awt.headless=true.

    This issue is solved in the AEM Cloud Service SDK version 19149 and later.

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/create-application-project/build-environment-details#pipeline-variables

 

Please try without custom code first. Delete crx-quickstart, set-up a new instance,

If it works, then we might need to update dependencies in project.

Aanchal Sikka
View in thread

2 replies

konstantyn_diachenko
Community Advisor
konstantyn_diachenkoCommunity Advisor
Community Advisor
Feb 13, 2025 9:32 PM UTC

Hi @aaron_dempwolff ,

 

Please check this official documentation and ensure that you migrated your project dependencies as well: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/create-application-project/build-environment-details#using-java-support 

Here you can find a good documentation wrote by our colleague: https://meticulous.digital/blog/f/upgrading-from-java-11-to-java-21-a-guide-for-aem-developers 

 

Best regards,

Kostiantyn Diachenko.

Translate
Kostiantyn Diachenko, Community Advisor, Certified Senior AEM Developer, creator of free AEM VLT Tool, maintainer of AEM Tools plugin.
    aanchal-sikka
    Community Advisor
    aanchal-sikkaCommunity AdvisorAccepted solution
    Community Advisor
    Feb 14, 2025 9:11 AM UTC

    Adobe documentation suggests

     

    The AEM Cloud Service SDK is compatible with Java 21 and can be used to validate the compatibility of your project with Java 21 before executing a Cloud Manager pipeline.

    • Edit a runtime parameter:
      When running AEM locally with Java 21, the start scripts (crx-quickstart/bin/start or crx-quickstart/bin/start.bat) fail due to the MaxPermSize parameter. As a remedy, either remove -XX:MaxPermSize=256M from the script or define the environment variable CQ_JVM_OPTS, setting it to -Xmx1024m -Djava.awt.headless=true.

      This issue is solved in the AEM Cloud Service SDK version 19149 and later.

    https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/create-application-project/build-environment-details#pipeline-variables

     

    Please try without custom code first. Delete crx-quickstart, set-up a new instance,

    If it works, then we might need to update dependencies in project.

    Translate
    Aanchal Sikka
      Terms & ConditionsAccessibility statement

      Loading footer...