Cette conversation a été verrouillée en raison de son inactivité. Veuillez créer une nouvelle publication.
Niveau 1
Niveau 2
Se connecter à la communauté
Connectez-vous pour voir tous les badges
Cette conversation a été verrouillée en raison de son inactivité. Veuillez créer une nouvelle publication.
Hi All,
I am facing very weird issue, after I restart my AEM 6.2 server using start.bat or quickstart.bat some of my classes are not loading properly and I am getting this below error.
org.apache.sling.scripting.sightly.SightlyException: Cannot find a a file corresponding to class org.apache.sling.scripting.sightly.<component-path>.SightlyJava_page in the repository. at org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileRepositoryJavaClass(SightlyJavaCompilerService.java:212) at org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.getInstance(SightlyJavaCompilerService.java:113) at org.apache.sling.scripting.sightly.impl.engine.UnitLoader.createUnit(UnitLoader.java:103) at org.apache.sling.scripting.sightly.impl.engine.SightlyScriptEngine.evaluateScript(SightlyScriptEngine.java:91) at org.apache.sling.scripting.sightly.impl.engine.SightlyScriptEngine.eval(SightlyScriptEngine.java:78) at org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:388) at org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:184) at org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:491) at org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:546) at org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:44)
But when I start my server by clicking on the AEM jar itself it works fine, any idea what could be reason for this.
Thanks,
Shehjad
Résolu ! Accéder à la solution.
Vues
Réponses
Nombre de J’aime
Hi Shehjad,
I faced a similar problem, it is resolved by setting the correct JDK version / JAVA_HOME. the AEM 6.x version needs a minimum of Java 8 in its environment/path.
Please set those and the SIGHTLY issue should be resolved.
thanks
Venkat
Vues
Réponses
Nombre de J’aime
Log does not help much, However, There are many configurations & API which are being loaded at the start of the AEM application. For instance, sling.properties file. This might be an issue in AEM 6.2
Raise a support ticket.
Regards,
Jitendra
Vues
Réponses
Nombre de J’aime
Hi Shehjad,
I faced a similar problem, it is resolved by setting the correct JDK version / JAVA_HOME. the AEM 6.x version needs a minimum of Java 8 in its environment/path.
Please set those and the SIGHTLY issue should be resolved.
thanks
Venkat
Vues
Réponses
Nombre de J’aime
Hi Shehjad,
In start up script mention the right java version to pick up. Also retain only the latest jar at <cq_home>/crx-quickstart/app/cq-quickstart-6.x.x-standalone-quickstart.jar
Thanks,
Vues
Réponses
Nombre de J’aime