Issues after applying SP1 to AEM 6.1 instance

Avatar

Avatar

au4liferz

Avatar

au4liferz

au4liferz

11-02-2016

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: }

Replies

Avatar

Avatar

bipinb4448661

Avatar

bipinb4448661

bipinb4448661

17-02-2016

Did we find resolution for this I am also facing same issue. Below are few errors I see while startup.

18.02.2016 06:01:29.241 *ERROR* [FelixStartLevel] ERROR: Error starting fileinstallpatch:/com.adobe.granite.contexthub.commons-0.0.36.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle com.adobe.granite.contexthub.commons [444]: Unable to resolve 444.0: missing requirement [444.0] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.widget)(version>=5.5.0)(!(version>=6.0.0))))

org.osgi.framework.BundleException: Unresolved constraint in bundle com.adobe.granite.contexthub.commons [444]: Unable to resolve 444.0: missing requirement [444.0] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.widget)(version>=5.5.0)(!(version>=6.0.0)))

    at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4095)

    at org.apache.felix.framework.Felix.startBundle(Felix.java:2114)

    at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1368)

    at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

    at java.lang.Thread.run(Thread.java:745)

18.02.2016 06:01:29.244 *ERROR* [FelixStartLevel] ERROR: Error starting fileinstallpatch:/cq-address-1.1.6.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle com.adobe.cq.cq-address [445]: Unable to resolve 445.0: missing requirement [445.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.address.api)(version>=1.0.0)(!(version>=1.1.0))))

org.osgi.framework.BundleException: Unresolved constraint in bundle com.adobe.cq.cq-address [445]: Unable to resolve 445.0: missing requirement [445.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.address.api)(version>=1.0.0)(!(version>=1.1.0)))

    at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4095)

    at org.apache.felix.framework.Felix.startBundle(Felix.java:2114)

    at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1368)

    at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

    at java.lang.Thread.run(Thread.java:745)

18.02.2016 06:01:29.252 *ERROR* [FelixStartLevel] ERROR: Error starting fileinstallpatch:/cq-content-insight-1.1.14.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle com.adobe.cq.cq-content-insight [446]: Unable to resolve 446.0: missing requirement [446.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.contentinsight)(version>=1.0.0)(!(version>=1.1.0))))

org.osgi.framework.BundleException: Unresolved constraint in bundle com.adobe.cq.cq-content-insight [446]: Unable to resolve 446.0: missing requirement [446.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.contentinsight)(version>=1.0.0)(!(version>=1.1.0)))

    at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4095)

    at org.apache.felix.framework.Felix.startBundle(Felix.java:2114)

    at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1368)

    at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

    at java.lang.Thread.run(Thread.java:745)

18.02.2016 06:01:29.253 *ERROR* [FelixStartLevel] ERROR: Error starting fileinstallpatch:/cq-experiencelog-1.0.12.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle com.adobe.cq.cq-experiencelog [447]: Unable to resolve 447.0: missing requirement [447.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.experiencelog)(version>=1.0.0)(!(version>=2.0.0))))

org.osgi.framework.BundleException: Unresolved constraint in bundle com.adobe.cq.cq-experiencelog [447]: Unable to resolve 447.0: missing requirement [447.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.experiencelog)(version>=1.0.0)(!(version>=2.0.0)))

    at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4095)

    at org.apache.felix.framework.Felix.startBundle(Felix.java:2114)

    at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1368)

    at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

    at java.lang.Thread.run(Thread.java:745)

18.02.2016 06:01:29.254 *ERROR* [FelixStartLevel] ERROR: Error starting fileinstallpatch:/cq-mcm-campaign-1.0.20.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle com.day.cq.mcm.cq-mcm-campaign [448]: Unable to resolve 448.0: missing requirement [448.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.mcm.campaign)(version>=1.0.0)(!(version>=2.0.0))))

org.osgi.framework.BundleException: Unresolved constraint in bundle com.day.cq.mcm.cq-mcm-campaign [448]: Unable to resolve 448.0: missing requirement [448.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.mcm.campaign)(version>=1.0.0)(!(version>=2.0.0)))

    at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4095)

    at org.apache.felix.framework.Felix.startBundle(Felix.java:2114)

    at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1368)

    at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

    at java.lang.Thread.run(Thread.java:745)

18.02.2016 06:01:29.255 *ERROR* [FelixStartLevel] ERROR: Error starting fileinstallpatch:/cq-mcm-core-5.9.10.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle com.day.cq.mcm.cq-mcm-core [449]: Unable to resolve 449.0: missing requirement [449.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.granite.security.user)(version>=1.2.0)(!(version>=2.0.0))))

org.osgi.framework.BundleException: Unresolved constraint in bundle com.day.cq.mcm.cq-mcm-core [449]: Unable to resolve 449.0: missing requirement [449.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.granite.security.user)(version>=1.2.0)(!(version>=2.0.0)))

    at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4095)

    at org.apache.felix.framework.Felix.startBundle(Felix.java:2114)

    at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1368)

    at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

    at java.lang.Thread.run(Thread.java:745)

18.02.2016 06:01:29.256 *ERROR* [FelixStartLevel] ERROR: Error starting fileinstallpatch:/cq-mcm-emailprovider-1.2.6.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle com.day.cq.mcm.cq-mcm-emailprovider [450]: Unable to resolve 450.0: missing requirement [450.0] osgi.wiring.package; (osgi.wiring.package=com.day.cq.commons.inherit))

org.osgi.framework.BundleException: Unresolved constraint in bundle com.day.cq.mcm.cq-mcm-emailprovider [450]: Unable to resolve 450.0: missing requirement [450.0] osgi.wiring.package; (osgi.wiring.package=com.day.cq.commons.inherit)

    at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4095)

    at org.apache.felix.framework.Felix.startBundle(Felix.java:2114)

    at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1368)

    at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

    at java.lang.Thread.run(Thread.java:745)

18.02.2016 06:01:29.258 *ERROR* [FelixStartLevel] ERROR: Error starting fileinstallpatch:/cq-mcm-exacttarget-integration-1.2.8.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle com.day.cq.mcm.cq-mcm-exacttarget-integration [451]: Unable to resolve 451.0: missing requirement [451.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.granite.crypto)(version>=1.1.0)(!(version>=2.0.0))))

org.osgi.framework.BundleException: Unresolved constraint in bundle com.day.cq.mcm.cq-mcm-exacttarget-integration [451]: Unable to resolve 451.0: missing requirement [451.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.granite.crypto)(version>=1.1.0)(!(version>=2.0.0)))

    at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4095)

    at org.apache.felix.framework.Felix.startBundle(Felix.java:2114)

    at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1368)

    at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

    at java.lang.Thread.run(Thread.java:745)

18.02.2016 06:01:29.259 *ERROR* [FelixStartLevel] ERROR: Error starting fileinstallpatch:/cq-mcm-landingpage-1.2.6.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle com.day.cq.mcm.cq-mcm-landingpage [452]: Unable to resolve 452.0: missing requirement [452.0] osgi.wiring.package; (osgi.wiring.package=com.day.cq.commons.jcr))

org.osgi.framework.BundleException: Unresolved constraint in bundle com.day.cq.mcm.cq-mcm-landingpage [452]: Unable to resolve 452.0: missing requirement [452.0] osgi.wiring.package; (osgi.wiring.package=com.day.cq.commons.jcr)

    at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4095)

    at org.apache.felix.framework.Felix.startBundle(Felix.java:2114)

    at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1368)

    at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

    at java.lang.Thread.run(Thread.java:745)

Avatar

Avatar

alin7ilie

Avatar

alin7ilie

alin7ilie

14-03-2016

So was this solved? I'm seeing the exact same issue.

Avatar

Avatar

au4liferz

Avatar

au4liferz

au4liferz

14-03-2016

 

bsloki wrote...

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

 

I logged daycare tickets, but they were not able to help. They had me go through all of the basic steps, but ultimately told me to restore from my backup, (which isn't much helped in resolving the root cause of this issue). Seems as if whenever problem resolution is really tough, the default answer is to "restore from your backup" smiley

Avatar

Avatar

jerrys49113842

Avatar

jerrys49113842

jerrys49113842

14-03-2016

I did the same. Support couldn't help me. 

As I was updating more machines and I forgot to login as "admin"  in one instance, I guessed that it was that machine. Installing the SP1 as user with "admin role" isn't the same as installing it as user "admin".

 

JS

Avatar

Avatar

au4liferz

Avatar

au4liferz

au4liferz

14-03-2016

alin7ilie wrote...

So was this solved? I'm seeing the exact same issue.

 

As bsloki suggested, please log a daycare ticket and then report back with the resolution. If enough of us log tickets, they may go ahead and determine the root cause of the issue instead of just saying you should restore from your backup, (which really isn't a resolution at all).

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K
smacdonald2008

15-03-2016

Heard back from support Eng members: 

I saw the same exact issue with a customer yesterday.  We were able to fix it by going to /system/console/slingjsp and force recompiling of the jsp files.

Avatar

Avatar

bsloki

MVP

Avatar

bsloki

MVP

bsloki
MVP

15-03-2016

Thanks @scott - that would help. I have done that and it works ! 

But can you check with them why do we have to do ? As it jsp has to be compiled every time you start an instance.

Avatar

Avatar

deisbel_diaz

Avatar

deisbel_diaz

deisbel_diaz

08-04-2016

It does not work for me. I'm still having the same problem. 

Avatar

Avatar

vishwanath881

Avatar

vishwanath881

vishwanath881

12-04-2016

It works some times but not all the time. 

Any update on this ?

Avatar

Avatar

cqvoyager

Avatar

cqvoyager

cqvoyager

03-06-2016

I'm getting this issue in the QA environment after restarting the AEM instance. I tried recompiling the jsp classes as mentioned in the release notes but of no use.

https://docs.adobe.com/docs/en/aem/6-1/release-notes-sp1.html

Accessing touch-optimized UI while 6.1 SP1 is getting installed can cause JSP compilation problem with error like below. To resolve this issue, clear the compiled classes using the web console plug-in available at http://<host>:<port>/system/console/slingjsp
*ERROR*​ [GET /projects HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException java.lang.Error: Unresolved compilation problems: Only a type can be imported. com.adobe.cq.experiencelog.ExperienceLogConfig resolves to a package

Additional information is some of the bundles are in installed state. Bundle information: 452 bundles in total, 420 bundles active, 8 active fragments, 24 bundles installed