Issues after applying SP1 to AEM 6.1 instance

[#1]

After installing AEM-6.1-Service-Pack-1 I can't reach several sites within AEM, (even the main page at http://localhost:4502/projects.html). I get the error listed below, informing me that there are issues in  /libs/cq/experiencelog/components/head/head.jsp. This is listed as a "Known issue", and the fix is supposed to be fairly simple, (just recompile the JSPs). I've tried the following things, to no avail. The issue is still there.

1. Gone to http://localhost:4502/system/console/slingjsp, and hit the "Recompile all JSPs" button. Restarted AEM. How do I know that the JSPs have really been recompiled? I can no longer look off of /var/classes to delete the classes, and see the new ones generated. When I look on the disk at .../author/crx-quickstart/launchpad/felix/bundle218/data/classes, I don't see the date for the classes changing. I've even stopped AEM, deleted the "classes" folder, and then restarted. It will regenerate the classes folder, but how do I ensure that all JSPs, (such as the head.jsp) is recompiled??? How can I verify that they have all been regenerated, (since I can't look off of /var/classes any longer)?

2. I've rebuilt the SP1 package, and re-installed it, to no avail.

So, how do I fix this? How did others fix this? I wasn't using AEM when I applied the Service Pack, (though I did have multiple windows open to CRXDE lite, and several other sites). Could this possibly be a java version mismatch issue? Even so, recompiling all of the JSPs should clear it up, (unless I need to build certain modules prior to compiling them to ensure that annotations, (e.g. @Component, are translated correctly etc.)).

Error:

Cannot serve request to /projects.html in /libs/cq/experiencelog/components/head/head.jsp Exception: org.apache.sling.scripting.jsp.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 6 in the generated java file Only a type can be imported. com.adobe.cq.experiencelog.ExperienceLogConfig resolves to a package An error occurred at line: 24 in the jsp file: /libs/cq/experiencelog/components/head/head.jsp ExperienceLogConfig cannot be resolved to a type 21: %><%@taglib prefix="cq" uri="http://www.day.com/taglibs/cq/1.0" %><% 22: %><cq:defineObjects /><% 23: 24: ExperienceLogConfig experienceLogConfig = sling.getService(ExperienceLogConfig.class); 25: if (experienceLogConfig.isEnabled(slingRequest)) { 26:     %><script src="<%=xssAPI.encodeForHTMLAttr(experienceLogConfig.getTrackingScript())%>"></script><% 27: }

[#2]

Was 218 the bundle ID for the org.apache.sling.commons.fsclassloader bundle as seen in the system console. If you delete all the class files on the hard disk, are they re-created when you restart and open the projects.html page?

Regards,

Opkar

[#3]

Opkar Gill wrote...

Was 218 the bundle ID for the org.apache.sling.commons.fsclassloader bundle as seen in the system console. If you delete all the class files on the hard disk, are they re-created when you restart and open the projects.html page?

Regards,

Opkar

Yes, 218 was the bundle ID for the FSC ClassLoader, and yes again, when I deleted the "classes" folder, and restarted AEM, it re-generated the "classes folder", (so I know all JSPs under that folder were re-generated, and I'm ASSUMING that they were  re-built, and re-compiled in order to re-generate them).

Note: to potentially improve the Adobe documentation, (e.g. Installation notes etc.). The documentation tells you to locate the bundle ID for the FSC ClassLoader, but don't tell you how to do that, (in detailed steps). It also tells you to "recompile all JSPs", but doesn't go into detail telling new users exactly how to do that either.

[#4]

You mentioned a Java versions mismatch, did you change the version of java you were using after the upgrade? 

Regards,

Opkar

[#5]

It looks like an issue. Even I am facing the same problem. Please log a daycare ticket

[#6]

Opkar Gill wrote...

You mentioned a Java versions mismatch, did you change the version of java you were using after the upgrade? 

Regards,

Opkar

No, but I was just thinking that perhaps, the version of java that Adobe used to compile the JSPs that were included in the SP1 package, might be different from the JVM that I'm running on, (which I've seen cause issues before). That's why I want to know how I can verify that all of the JSPs have been re-compiled, (i.e. both specific/individual JSPs, and also, if I wanted to recompile every JSP in AEM). It was easy to do that in AEM 5.61 and earlier versions, but now that they no longer store compiled classes under /var/classes, it seems to be very tough to know where to look for each JSP on the disk, (unless they are all under the FSC ClassLoader directory).

[#7]

I see this issue only with /projects.html

but I am able to access all other URLs like /welcome.html, /crx/de, /system/console etc..

[#8]

I just started my instance with SP1 and did not get the issue with "/projects.html". For the original issue, I'd raise a daycare ticket and see if support can help you out.

Regards,

Opkar

[#9]

bsloki wrote...

I see this issue only with /projects.html

but I am able to access all other URLs like /welcome.html, /crx/de, /system/console etc..

That's correct. It's only ../project.html, and a few other .html pages, (i.e. all of the touch UI stuff).

[#10]

any news on this issue?

We have the same problem and rely heavily on the touch UI.