Bundles going in installed state after service pack install

[sjb99]

Hi,

I installed service pack 8 on a fresh AEM 6.5 instance in my mac machine. 37 bundles go into Install state which were previously active before service pack. I tried multiple times by setting up fresh instance again but its the same thing. What could be the solution?

[Ravi_Pampana]

Hi,

Can you check by expanding the bundles and see whether there are any unresolved bundles which has version conflicts ? Also, check whether the uber jar was updated to the correct AEM version. 

[sjb99]

Thanks for responding. Where do I correct the uber jar? Because I'm not installing my project. It's just the service pack which I installed. In few bundles there is some version mismatch and is highlighted in red. But what do I do to resolve it? It's a complete fresh installation and only Adobe given package is installed. Same thing happening with SP7 too

[Ravi_Pampana]

What is the version of Java you are having and did you see any errors in the log files (error.log) ? What is the process you are following to upgrade ? Is it installing Service pack 8 on plan version of AEM 6.5 ?

[sjb99]

@Ravi_Pampana Thanks for responding. Where do I correct the uber jar? Because I'm not installing my project. It's just the service pack which I installed. In few bundles there is some version mismatch and is highlighted in red. But why is showing such error? It's a complete fresh installation and only Adobe given package is installed. Same thing happening with SP7 too

[Jörg_Hoh]

Have you restarted the instance? IIRC that's what Adobe mandates.

[sjb99]

Hi @Jörg_Hoh , yes I restarted it multiple times. even tried setting up fresh instance again and restarted it multiple times but same issue after install SP8 or even SP7 for that matter.

[sjb99]

@Ravi_Pampana @Jörg_Hoh Hi, thank you for the responses. I'm using JDK 11.0.10 which I downloaded from Adobe. This is a fresh installation where I'm installing on plain AEM 6.5 instance. Literally opening the cq jar for the first time, once its up and all bundles are fine, I restart it and I install SP8 and restart it again after the package is installed after 45 mins or so. I even started waiting that long for better results but the behavior is same. Could this be due to my Mac version? I'm using Mac 10.12.6 (Sierra). Please find the error log. So many unsresolved bundles due to some mismatch. This is a fresh installation, so I don't understand how mismatch can come up. Please help.

13.04.2021 01:40:38.405 *ERROR* [FelixDispatchQueue] com.day.cq.mcm.cq-mcm-emailprovider FrameworkEvent ERROR (org.osgi.framework.BundleException: Unable to resolve com.day.cq.mcm.cq-mcm-emailprovider [364](R 364.0): missing requirement [com.day.cq.mcm.cq-mcm-emailprovider [364](R 364.0)] osgi.wiring.package; (osgi.wiring.package=com.day.cq.wcm.foundation.forms) [caused by: Unable to resolve com.day.cq.wcm.cq-wcm-foundation [468](R 468.1): missing requirement [com.day.cq.wcm.cq-wcm-foundation [468](R 468.1)] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.wcm.ui.components.container.service)(version>=1.0.0)(!(version>=2.0.0)))] Unresolved requirements: [[com.day.cq.mcm.cq-mcm-emailprovider [364](R 364.0)] osgi.wiring.package; (osgi.wiring.package=com.day.cq.wcm.foundation.forms)])
org.osgi.framework.BundleException: Unable to resolve com.day.cq.mcm.cq-mcm-emailprovider [364](R 364.0): missing requirement [com.day.cq.mcm.cq-mcm-emailprovider [364](R 364.0)] osgi.wiring.package; (osgi.wiring.package=com.day.cq.wcm.foundation.forms) [caused by: Unable to resolve com.day.cq.wcm.cq-wcm-foundation [468](R 468.1): missing requirement [com.day.cq.wcm.cq-wcm-foundation [468](R 468.1)] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.wcm.ui.components.container.service)(version>=1.0.0)(!(version>=2.0.0)))] Unresolved requirements: [[com.day.cq.mcm.cq-mcm-emailprovider [364](R 364.0)] osgi.wiring.package; (osgi.wiring.package=com.day.cq.wcm.foundation.forms)]
	at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368)
	at org.apache.felix.framework.Felix.startBundle(Felix.java:2281)
	at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1539)
	at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
	at java.base/java.lang.Thread.run(Thread.java:834)

[sjb99]

hi @Jörg_Hoh @kautuk_sahni any help or pointers regarding this please? Tried everything with different java versions also

[Jörg_Hoh]

Can you try to start bundles manually and see if that unblocks this situation? IIRC I had this behaviour sometimes (and it's definitely not planned to behave like this). 

[ravir73578276]

Hy @sjb99 , were you able to fix this issue? I am also facing similar issue on my centos virtual machine. If yes, please provide the RCA.