Is AEM 6.5 LTS In-Place upgrade not possible in our case?

[Rajumuddana]

Hi All,

In continuation to this https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/what-is-the-process-of-run...

I tried do the step to check whether the existed 'crx-quickstart' would work with LTS jar file(), so started the jar file along side 'crx-quickstart', but that is failed to start seamlessly, with below errors,

ex:

*ERROR* [FelixLogListener] Events.Framework.org.apache.jackrabbit.oak-segment-azure FrameworkEvent ERROR (org.apache.felix.log.LogException: org.osgi.framework.BundleException: Unable to resolve org.apache.jackrabbit.oak-segment-azure [120](R 120.2): missing requirement [org.apache.jackrabbit.oak-segment-azure [120](R 120.2)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.jackrabbit.oak.segment.spi.persistence.split)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve org.apache.jackrabbit.oak-segment-tar [121](R 121.2): missing requirement [org.apache.jackrabbit.oak-segment-tar [121](R 121.2)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.jackrabbit.oak.plugins.blob.datastore)(version>=0.0.0)(!(version>=1.0.0))) [caused by: Unable to resolve org.apache.jackrabbit.oak-blob-plugins [112](R 112.2): missing requirement [org.apache.jackrabbit.oak-blob-plugins [112](R 112.2)] osgi.wiring.package; (osgi.wiring.package=java.sql)]] Unresolved requirements: [[org.apache.jackrabbit.oak-segment-azure [120](R 120.2)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.jackrabbit.oak.segment.spi.persistence.split)(version>=1.0.0)(!(version>=2.0.0)))])

org.apache.felix.log.LogException: org.osgi.framework.BundleException: Unable to resolve org.apache.jackrabbit.oak-segment-azure [120](R 120.2): missing requirement [org.apache.jackrabbit.oak-segment-azure [120](R 120.2)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.jackrabbit.oak.segment.spi.persistence.split)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve org.apache.jackrabbit.oak-segment-tar [121](R 121.2): missing requirement [org.apache.jackrabbit.oak-segment-tar [121](R 121.2)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.jackrabbit.oak.plugins.blob.datastore)(version>=0.0.0)(!(version>=1.0.0))) [caused by: Unable to resolve org.apache.jackrabbit.oak-blob-plugins [112](R 112.2): missing requirement [org.apache.jackrabbit.oak-blob-plugins [112](R 112.2)] osgi.wiring.package; (osgi.wiring.package=java.sql)]] Unresolved requirements: [[org.apache.jackrabbit.oak-segment-azure [120](R 120.2)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.jackrabbit.oak.segment.spi.persistence.split)(version>=1.0.0)(!(version>=2.0.0)))]

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

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

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

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

        at java.base/java.lang.Thread.run(Thread.java:840)

These errors made me to lean towards 'in-place' upgrade is not possible in our case.

Or is there any aspect I should check before conclude?

Thanks,

Raju.

[giuseppebaglio · Accepted solution]

hi @Rajumuddana, 

Could it be that you didn't perform the required unpacking step before running the new LTS jar with the old crx-quickstart folder? This approach causes OSGi bundle version mismatches between the new AEM version and the existing repository structure.

Before starting the instance (guide here), you must unpack the new AEM 6.5 LTS jar file:

java -Xmx4096m -jar aem-quickstart-6.5-lts.jar -unpack

This step extracts updated OSGi bundles, libraries, and configurations that are required for compatibility with your existing repository.