Skip to main content
R
RobertInfosys
New Participant
May 27, 2021

Sling rendering fails after a few builds

  • May 27, 2021
  • 12 replies
  • 5626 views

I am a developer and I have a local instance I use for building and testing. My system is using the Java 11 JDK. After some number of builds, I haven't counted but the instance is fine for a bit then fails. The builds are successful and deploy fine. The issue I'm running into is that something happens where the pages I have created no longer render. In fact, neither do the WE Retail pages. The response to the request to the page is an empty document. The only way I have been able to fix it is by deleting the entire crx-quickstart tree then rebuilding the instance. This is time consuming and painful. I loose all of my configurations and changes that aren't backed up in a package, those that are, require me to then load the package after the instance has rebuilt. I have tried compacting the indexes and forcing them to rebuild but that doesn't work.

 

Has anyone else had a similar issue and if you were able to fix it, how did you do so?

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

    12 replies

    Asutosh_Jena_
    Asutosh_Jena_
    New Participant
    May 28, 2021

    Hi @robertinfosys 

     

    This is a known issue with AEM 6.5 running on JDK 11. This issue is due to the fact that CXF packages have been removed from AEM and you have to install those externally while running on JDK 11.

    You will need to replace the below line in sling.properties file present inside crx-quickstart/conf

     

    sling.bootdelegation.sun=sun.*,com.sun.*
    with
    sling.bootdelegation.sun=sun.*,com.sun.*,jdk.internal.reflect,jdk.internal.reflect.*
     
    Restart the instance. You will never face the issue again and all the pages will render fine.
     
     
    Thanks!
      R
      RobertInfosysAuthor
      New Participant
      May 28, 2021
      First attempt. Stopped the instance, changed the property, restarted, the authentication service failed. Couldn't log into anything so I had to delete the crx-quickstart folder and start over. I changed the property after the instance was recreated and restarted. I'll see if this fixes it and report back.
      T
      troubleshooter3
      New Participant
      May 27, 2021

      This happened with me as well on AEM 6.5 with Java 11. Couldnt find solution and end up using Java 8 

        R
        RobertInfosysAuthor
        New Participant
        May 27, 2021
        That was kind of my guess. However, the specifications say that 6.5 is supposed to be compatible with Java 11 and because of security from where I'm working, downloading and installing Java 8 isn't easy to do.
          Prince_Shivhare
          Prince_Shivhare
          New Participant
          May 27, 2021

          Can you please check error.log?

          which can help us to find the exact error.

            R
            RobertInfosysAuthor
            New Participant
            May 27, 2021
            I had checked the logs before and it didn't provide much help. I searched based on the exception. I don't remember but it was something with the Sling Default Servlet.
              R
              RobertInfosysAuthor
              New Participant
              May 27, 2021
              Additional information: this project was created from the aem-project-archetype version 27 and using the 6.5 version of the runtime jar. 6.5.0 uber-jar.
                Terms & ConditionsAccessibility statement

                Loading footer...