AEM instance corrupted on startup | Community
Skip to main content
L
lucy.wang
Level 2
March 30, 2021
Solved

AEM instance corrupted on startup

  • March 30, 2021
  • 5 replies
  • 4208 views

Hello everyone, 

 

I am using AEM 6.5. I have a really weird problem on startup of the instance. Every time, when I shut off my instance and start it again, my AEM instance wouldn't work properly. The image on the splash screen as well as the icons in the touch UI wouldn't load. I had to delete the crx-quickstart to reinstall the instance. Then it will be fine. But next time, when I shut off the instance and start it again, same problem happens. I can't really delete the crx-quickstart every time since I have installed some packages and I had to redo them again. I was wondering if anyone know how to resolve this issue.

 

Thanks in advance for your help. 

 

Lucy 

    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 bilal_ahmad

    Hey @lucy.wang,

    Are you migrating from old AEM version to new one? Also, please let me know if I've understood incorrectly here:
    --> when you have a fresh instance(just after you unpack the jar) things work quite well.

    --> as soon as you install some packages and the the issue starts to happen(after you shut down the instance and restart)


    Is there is a possibility that you have custom oak:index definitions in your package? if that's the case please remove those paths(custom index definitions) from filter(while creating the package itself) and then try installing it.(check if you have queryPaths and includedPaths in your custom index definition)

     

    Also, if you leave your instance for a long while(2hours or so), does that resolve the issue on its own? please try that.

     

    Thanks,

    Bilal.

    5 replies

    Asutosh_Jena_
    Community Advisor
    Asutosh_Jena_Community Advisor
    Community Advisor
    March 30, 2021

    @Hi @lucy.wang 

    Can you confirm if you are using AEM 6.5 with JDK 8 or JDK 11.

    If you are using with JDK 11 you will need to ensure to add the below lines in the sling.properties file on your instance for sling.bootdelegation.sun property.

     

    File before update: sling.bootdelegation.sun=sun.*,com.sun.*

    After update: sling.bootdelegation.sun=sun.*,com.sun.*,jdk.internal.reflect,jdk.internal.reflect.*

     

     Also you can include the below snippet to your JVM parameters in the start.bat(Windows) or start.sh(Mac OS/Linux) file based on the OS.

     

    -XX:+UseParallelGC --add-opens=java.desktop/com.sun.imageio.plugins.jpeg=ALL-UNNAMED --add-opens=java.base/sun.net.www.protocol.jrt=ALL-UNNAMED --add-opens=java.naming/javax.naming.spi=ALL-UNNAMED --add-opens=java.xml/com.sun.org.apache.xerces.internal.dom=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED -Dnashorn.args=--no-deprecation-warning

     

    Also allow enough heap memory something like 2048 MB or 4096 MB.

     

    It will become something like:

    CQ_JVM_OPTS='-server -Xmx4096m -XX:MaxPermSize=256M -Djava.awt.headless=true -XX:+UseParallelGC --add-opens=java.desktop/com.sun.imageio.plugins.jpeg=ALL-UNNAMED --add-opens=java.base/sun.net.www.protocol.jrt=ALL-UNNAMED --add-opens=java.naming/javax.naming.spi=ALL-UNNAMED --add-opens=java.xml/com.sun.org.apache.xerces.internal.dom=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED -Dnashorn.args=--no-deprecation-warning'

     

    Please refer the Java 11 consideration section in the below article:

    https://experienceleague.adobe.com/docs/experience-manager-65/deploying/deploying/custom-standalone-install.html?lang=en#run-modes

     

    Hope this will help you!

    Thanks!

      L
      lucy.wangAuthor
      Level 2
      March 30, 2021
      Performing data store consistency check... error: java.lang.RuntimeException: Error occurred while obtaining InputStream for blobId [3e15c88da9b46267141b60826c0734007c3e5a5f804c953edb0280eda680a9be#174188]
      A
      abhishsh
      March 30, 2021
      Hi @lucy.wang, Do you see if there are any bundle in resolved or installed state at system console, after restart of instance and what's the error or exception you see in error log ?
      U
      Adobe Employee
      user05162Adobe Employee
      Adobe Employee
      March 30, 2021

      What error do you see in the log files? I would recommend checking log files for any errors.

        bilal_ahmad
        bilal_ahmadAccepted solution
        Level 5
        March 31, 2021

        Hey @lucy.wang,

        Are you migrating from old AEM version to new one? Also, please let me know if I've understood incorrectly here:
        --> when you have a fresh instance(just after you unpack the jar) things work quite well.

        --> as soon as you install some packages and the the issue starts to happen(after you shut down the instance and restart)


        Is there is a possibility that you have custom oak:index definitions in your package? if that's the case please remove those paths(custom index definitions) from filter(while creating the package itself) and then try installing it.(check if you have queryPaths and includedPaths in your custom index definition)

         

        Also, if you leave your instance for a long while(2hours or so), does that resolve the issue on its own? please try that.

         

        Thanks,

        Bilal.

          U
          Adobe Employee
          user05162Adobe Employee
          Adobe Employee
          March 31, 2021

          Error[1] means something wrong with your datastore. Either the user running AEM does not have permissions to the crx-quickstart/repository/datastore folder or something else going on with the datastore.

           

          [1] error: java.lang.RuntimeException: Error occurred while obtaining InputStream for blobId [3e15c88da9b46267141b60826c0734007c3e5a5f804c953edb0280eda680a9be#174188]

            Terms & ConditionsAccessibility statement

            Loading footer...