Unable to compile class for JSP: An error occurred at line: 6 in the generated java file Only a type can be imported.

[suvasishm]

Problem:

On Author http://<host:port>/projects.html getting the following error after AEM 6.1 SP1 installation:

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
 

On Publish http://<host:port>/content/geometrixx-outdoors/en.html getting the following error after SP1 installation:
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.granite.contexthub.api.ContextHub resolves to a package An error occurred at line: 54 in the jsp file: /libs/granite/contexthub/components/contexthub/contexthub.jsp ContextHub cannot be resolved to a type

Pretty much similar errors. Need help fixing the problem.

Observation while debugging:

a) On both the environments Adobe Granite ContextHub Commons(com.adobe.granite.contexthub.commons) and Adobe CQ Experience Log Client Bundlecom.adobe.cq.cq-experiencelog bundles are in "installed" state. 

In fact on author, Bundle information: 455 bundles in total, 418 bundles active, 8 active fragments, 29 bundles installed 

and on publish Bundle information: 451 bundles in total, 415 bundles active, 8 active fragments, 28 bundles installed. 

So a large number of bundles are in "installed" state.

b) In the log:

13.06.2016 06:35:38.310 *ERROR* [qtp1771211259-95655] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unresolved constraint in bundle com.adobe.cq.cq-experiencelog [459]: Unable to resolve 459.0: missing requirement [459.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 [459]: Unable to resolve 459.0: missing requirement [459.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.experiencelog)(version>=1.0.0)(!(version>=2.0.0)))


Please suggest solution to fix the problem.

[smacdonald2008]

If your bundles are not in an active state - there is a bigger issue.  Try restarting AEM to see if the bundles become active. 

[suvasishm]

Tried with several restart. Same result. As many as 28 or 29 bundles remaining in "installed" state.

[Peter_Puzanovs]

Try going into: http://{ip}:{port}/system/console/bundles

Search for Adobe CQ Experience Log Client Bundle com.adobe.cq.cq-experiencelog

Would assume it is in the Stopped state, try pressing on the start button.

At the same time look through the error.log, do you see any problems there?

Regards,

Peter

[suvasishm]

Thank you Peter for your response.

Tried to start Adobe CQ Experience Log Client Bundle com.adobe.cq.cq-experiencelog from felix console, it won't start and here is the corresponding snippet from error log:

14.06.2016 04:31:01.179 *ERROR* [qtp480655781-349] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unresolved constraint in bundle com.adobe.cq.cq-experiencelog [451]: Unable to resolve 451.0: missing requirement [451.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 [451]: Unable to resolve 451.0: missing requirement [451.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.experiencelog)(version>=1.0.0)(!(version>=2.0.0)))
    

Regards,

Suvasish

[smacdonald2008]

You are missing some OSGi bundles that define OSGi dependencies such as  osgi.wiring.package. Did this just start acting up or did someone make a change to some bunldes. From this error log - it almost looks like some OSGi bundles were removed. 

[suvasishm]

The problem started only after installing SP1 and few other hot fixes. We didn't remove any bundle manually.

 

[smacdonald2008]

this looks like a bug (as opposed to a How To question that the community can help you with)- your best route would be to file a support ticket. 

https://helpx.adobe.com/marketing-cloud/contact-support.html

[suvasishm]

                Raised a support ticket already. Thanka nonetheless.

[smacdonald2008]

I wish we had an article to help with this - but this is a support issue. 

[suvasishm]

Thank you all for scratching your heads along with me . Got the problem resolved with support help.

[kautuk_sahni]

This is great that your problem is resolved now.

Please share the solution for community's benefit.

Thanks and Regards

Kautuk Sahni

[suvasishm · Accepted solution]

Steps that fixed the issue for me courtesy Daycare support.

1. Stopped Region Digraph (org.eclipse.equinox.region) bundle. Not used in 6.1.

2. Restart the instance

3. Clear the compiled classes using http://<host>:<port>/system/console/slingjsp

[kautuk_sahni]

suvasishm wrote...

Steps that fixed the issue for me courtesy Daycare support.

1. Stopped Region Digraph (org.eclipse.equinox.region) bundle. Not used in 6.1.

2. Restart the instance

3. Clear the compiled classes using http://<host>:<port>/system/console/slingjsp

Thank you.