Upgrade from 6.2 CE to 7.3 CE succeeds but OSGi services go missing

Jamie Sammons, modified 4 Years ago.

Junior Member Posts: 92 Join Date: 7/29/14 Recent Posts

Hello Liferay Community. Thank you beforehand for any help.

We have used the Upgrade Tool for going from 6.2.5 ga6 to 7.3.5 ga6, and at first it seems like the whole process worked well. There was only a single error to show up, which I though it was OK to ignore. The error in the upgrade was:

2020-11-12 02:36:02.808 ERROR [main][VerifyProcessTrackerOSGiCommands:289] com.liferay.portal.verify.VerifyException: com.liferay.document.library.kernel.exception.NoSuchFileVersionException: No DLFileVersion exists with the key {fileEntryId=2329238, version=1.0}
com.liferay.portal.verify.VerifyException: com.liferay.document.library.kernel.exception.NoSuchFileVersionException: No DLFileVersion exists with the key {fileEntryId=2329238, version=1.0}
        at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:74)
        at com.liferay.portal.verify.extender.internal.osgi.commands.VerifyProcessTrackerOSGiCommands.executeVerifyProcesses(VerifyProcessTrackerOSGiCommands.java:286)
        at com.liferay.portal.verify.extender.internal.osgi.commands.VerifyProcessTrackerOSGiCommands$1.run(VerifyProcessTrackerOSGiCommands.java:338)
        at com.liferay.portal.output.stream.container.internal.OutputStreamContainerFactoryTrackerImpl.runWithSwappedLog(OutputStreamContainerFactoryTrackerImpl.java:134)
        at com.liferay.portal.verify.extender.internal.osgi.commands.VerifyProcessTrackerOSGiCommands.executeVerifyProcesses(VerifyProcessTrackerOSGiCommands.java:333)
        at com.liferay.portal.verify.extender.internal.osgi.commands.VerifyProcessTrackerOSGiCommands._execute(VerifyProcessTrackerOSGiCommands.java:387)
        at com.liferay.portal.verify.extender.internal.osgi.commands.VerifyProcessTrackerOSGiCommands.access$200(VerifyProcessTrackerOSGiCommands.java:80)
        at com.liferay.portal.verify.extender.internal.osgi.commands.VerifyProcessTrackerOSGiCommands$VerifyServiceTrackerMapListener.keyEmitted(VerifyProcessTrackerOSGiCommands.java:462)
        at com.liferay.portal.verify.extender.internal.osgi.commands.VerifyProcessTrackerOSGiCommands$VerifyServiceTrackerMapListener.keyEmitted(VerifyProcessTrackerOSGiCommands.java:451)
        at com.liferay.osgi.service.tracker.collections.internal.map.ServiceTrackerMapImpl$DefaultEmitter.emit(ServiceTrackerMapImpl.java:209)
        at com.liferay.osgi.service.tracker.collections.map.PropertyServiceReferenceMapper.map(PropertyServiceReferenceMapper.java:50)
        at com.liferay.osgi.service.tracker.collections.internal.map.ServiceTrackerMapImpl$ServiceReferenceServiceTrackerCustomizer.addingService(ServiceTrackerMapImpl.java:241)
        at com.liferay.osgi.service.tracker.collections.internal.map.ServiceTrackerMapImpl$ServiceReferenceServiceTrackerCustomizer.addingService(ServiceTrackerMapImpl.java:229)
        at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:943)
        at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:1)
        at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
        at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:183)
        at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:321)
        at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:264)
        at com.liferay.osgi.service.tracker.collections.internal.map.ServiceTrackerMapImpl.&lt;init&gt;(ServiceTrackerMapImpl.java:60)
        at com.liferay.osgi.service.tracker.collections.map.ServiceTrackerMapFactory.openMultiValueMap(ServiceTrackerMapFactory.java:71)
        at com.liferay.portal.verify.extender.internal.osgi.commands.VerifyProcessTrackerOSGiCommands.activate(VerifyProcessTrackerOSGiCommands.java:209)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.apache.felix.scr.impl.inject.methods.BaseMethod.invokeMethod(BaseMethod.java:228)
        at org.apache.felix.scr.impl.inject.methods.BaseMethod.access$500(BaseMethod.java:41)
        at org.apache.felix.scr.impl.inject.methods.BaseMethod$Resolved.invoke(BaseMethod.java:664)
        at org.apache.felix.scr.impl.inject.methods.BaseMethod.invoke(BaseMethod.java:510)
        at org.apache.felix.scr.impl.inject.methods.ActivateMethod.invoke(ActivateMethod.java:310)
        at org.apache.felix.scr.impl.inject.methods.ActivateMethod.invoke(ActivateMethod.java:300)
        at org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:341)
        at org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:114)
        at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:983)
        at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:956)
        at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:756)
        at org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:1053)
        at org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:1007)
        at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1216)
        at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1137)
        at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:944)
        at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:880)
        at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1168)
        at org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:125)
        at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109)
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:891)
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:804)
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127)
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:228)
        at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:469)
        at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:906)
        at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:892)
        at org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:128)
        at org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:959)
        at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:732)
        at org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:1053)
        at org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:1007)
        at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1216)
        at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1137)
        at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:944)
        at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:880)
        at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1168)
        at org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:125)
        at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109)
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:891)
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:804)
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127)
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:228)
        at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:469)
        at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:487)
        at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:1004)
        at com.liferay.registry.internal.RegistryImpl.registerService(RegistryImpl.java:342)
        at com.liferay.portal.tools.DBUpgrader._registerModuleServiceLifecycle(DBUpgrader.java:236)
        at com.liferay.portal.tools.DBUpgrader._upgradeModules(DBUpgrader.java:297)
        at com.liferay.portal.tools.DBUpgrader.upgrade(DBUpgrader.java:158)
        at com.liferay.portal.tools.DBUpgrader.upgrade(DBUpgrader.java:144)
        at com.liferay.portal.tools.DBUpgrader.main(DBUpgrader.java:124)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at com.liferay.portal.tools.db.upgrade.client.DBUpgraderLauncher.main(DBUpgraderLauncher.java:54)
Caused by: com.liferay.document.library.kernel.exception.NoSuchFileVersionException: No DLFileVersion exists with the key {fileEntryId=2329238, version=1.0}
        at com.liferay.portlet.documentlibrary.service.persistence.impl.DLFileVersionPersistenceImpl.findByF_V(DLFileVersionPersistenceImpl.java:3670)
        at com.liferay.portlet.documentlibrary.service.impl.DLFileVersionLocalServiceImpl.getFileVersion(DLFileVersionLocalServiceImpl.java:78)
        at jdk.internal.reflect.GeneratedMethodAccessor201.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at com.liferay.portal.spring.aop.AopMethodInvocationImpl.proceed(AopMethodInvocationImpl.java:50)
        at com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:69)
        at com.liferay.portal.spring.aop.AopMethodInvocationImpl.proceed(AopMethodInvocationImpl.java:57)
        at com.liferay.portal.spring.aop.AopInvocationHandler.invoke(AopInvocationHandler.java:49)
        at com.sun.proxy.$Proxy136.getFileVersion(Unknown Source)
        at com.liferay.document.library.kernel.service.DLFileVersionLocalServiceUtil.getFileVersion(DLFileVersionLocalServiceUtil.java:361)
        at com.liferay.portlet.documentlibrary.model.impl.DLFileEntryImpl.getFileVersion(DLFileEntryImpl.java:195)
        at com.liferay.portlet.documentlibrary.model.impl.DLFileEntryImpl.getFileVersion(DLFileEntryImpl.java:190)
        at com.liferay.document.library.internal.verify.DLServiceVerifyProcess.updateFileEntryAssets(DLServiceVerifyProcess.java:315)
        at com.liferay.document.library.internal.verify.DLServiceVerifyProcess.doVerify(DLServiceVerifyProcess.java:240)
        at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:71)
        ... 82 more

But, when starting up the portal after the upgrade, we get a myriad of OSGi services missing.

After some research in the Liferay Community forum, something took our attention. The Release_table has a module: com.liferay.document.library.service whcih failed in the verify process, and as far as I understand, that's the reason for a 2 in the state_ column. By the way, you can see how the core upgrade ran smoothly (we are now working with the 7305 version though, that was a screenshot of the time we were on 7.3.4).

Sice we had run the upgrade without a copy of the document library locally...I thought we could run it again having it locally. So I got a copy of it...and after running the whole process again, we got to the same described problem. About this, I made sure I pointed the property to the particular document library directory in my local, so in my portal-upgrade-ext.properties I have:

liferay.home=C:/work/AoC/bundles/aoc-portal/bundles
dl.store.impl=com.liferay.portal.store.file.system.FileSystemStore
dl.store.file.system.root.dir=C:/Users/evaldeslacasa/AoC/aoc-doclib

If I go to the Apache GoGo console, everything related to the upgrade seems to be fine. If I run:

g! upgrade:check
g!

Nothing gets displayed, so it seems like the upgrade didn't have issues.

And if I run:

g! verify:checkAll
com.liferay.portal.scheduler.internal.verify verify process succeeded
com.liferay.portal.security.sso.cas verify process succeeded
com.liferay.systemevent.internal.verify verify process succeeded
com.liferay.polls.service verify process succeeded
com.liferay.mobile.device.rules.service verify process succeeded
com.liferay.portal.security.ldap verify process succeeded
com.liferay.portal.security.sso.opensso verify process succeeded
com.liferay.commerce.account.service verify process succeeded
com.liferay.portal.security.service.access.policy.service verify process succeeded
com.liferay.message.boards.service verify process succeeded
com.liferay.portal.security.sso.facebook.connect verify process succeeded
g!

It looks like everything succeeded.

Now, if I check for unresolved dependencies, then I get many of them (and interestingly, many related to Commerce):

g! dm wtf
13 unregistered components found
--------------------------------
The following service(s) are missing:
 * com.liferay.commerce.product.service.CPDefinitionLocalService for bundle com.liferay.commerce.service
 * com.liferay.commerce.product.service.CPDefinitionLocalService for bundle com.liferay.commerce.product.type.grouped.service
 * com.liferay.commerce.product.service.CommerceChannelLocalService for bundle com.liferay.commerce.tax.service
 * com.liferay.commerce.service.CommerceOrderItemLocalService for bundle com.liferay.commerce.product.type.virtual.order.service
 * com.liferay.journal.service.JournalArticleLocalService for bundle com.liferay.commerce.product.type.virtual.service
 * com.liferay.commerce.product.service.CPDefinitionLocalService for bundle com.liferay.commerce.product.type.virtual.service
 * com.liferay.commerce.product.service.CPDefinitionLocalService for bundle com.liferay.commerce.wish.list.service
 * com.liferay.commerce.product.service.CommerceChannelLocalService for bundle com.liferay.commerce.tax.engine.fixed.service
 * com.liferay.commerce.product.service.CommerceCatalogService for bundle com.liferay.commerce.price.list.service
 * com.liferay.commerce.product.service.CPInstanceService for bundle com.liferay.commerce.price.list.service
 * com.liferay.commerce.product.service.CProductLocalService for bundle com.liferay.commerce.wish.list.service
 * com.liferay.commerce.discount.service.CommerceDiscountLocalService for bundle com.liferay.commerce.service
 * com.liferay.commerce.product.service.CommerceChannelLocalService for bundle com.liferay.commerce.shipping.engine.fixed.service
 * com.liferay.commerce.service.CommerceSubscriptionEntryLocalService for bundle com.liferay.commerce.product.type.virtual.order.service
 * com.liferay.commerce.product.service.CommerceCatalogLocalService for bundle com.liferay.commerce.product.type.grouped.service
 * com.liferay.commerce.product.service.CommerceChannelLocalService for bundle com.liferay.commerce.payment.service
 * com.liferay.commerce.product.service.CProductLocalService for bundle com.liferay.commerce.product.type.grouped.service
 * com.liferay.commerce.product.service.CProductLocalService for bundle com.liferay.commerce.product.type.virtual.service
 * com.liferay.commerce.product.service.CPInstanceLocalService for bundle com.liferay.commerce.wish.list.service
 * com.liferay.journal.service.JournalArticleService for bundle com.liferay.commerce.product.type.virtual.service
 * com.liferay.commerce.product.service.CPInstanceLocalService for bundle com.liferay.commerce.price.list.service
 * com.liferay.commerce.product.service.CPInstanceLocalService for bundle com.liferay.commerce.service
 * com.liferay.commerce.service.CommerceAddressRestrictionLocalService for bundle com.liferay.commerce.payment.service
 * com.liferay.portal.kernel.model.Release (&amp;(release.bundle.symbolic.name=com.liferay.document.library.service)(&amp;(release.schema.version&gt;=3.1.0)(!(release.schema.version&gt;=4.0.0)))(|(!(release.state=*))(release.state=0))) for bundle com.liferay.document.library.service
 * com.liferay.commerce.product.service.CPDefinitionOptionRelLocalService for bundle com.liferay.commerce.service
 * com.liferay.commerce.product.permission.CommerceProductViewPermission for bundle com.liferay.commerce.wish.list.service
 * com.liferay.commerce.product.service.CommerceChannelLocalService for bundle com.liferay.commerce.service
 * com.liferay.commerce.product.service.CommerceCatalogLocalService for bundle com.liferay.commerce.product.type.virtual.service
 * com.liferay.commerce.product.service.CPInstanceLocalService for bundle com.liferay.commerce.product.type.virtual.service
 * com.liferay.commerce.product.type.virtual.service.CPDefinitionVirtualSettingLocalService for bundle com.liferay.commerce.product.type.virtual.order.service
 * com.liferay.commerce.product.service.CommerceChannelService for bundle com.liferay.commerce.service
 * com.liferay.commerce.product.service.CommerceChannelService for bundle com.liferay.commerce.discount.service
 * com.liferay.commerce.product.service.CommerceCatalogLocalService for bundle com.liferay.commerce.service
 * com.liferay.commerce.price.CommerceProductPriceCalculationFactory for bundle com.liferay.commerce.service
 * com.liferay.commerce.tax.CommerceTaxCalculation for bundle com.liferay.commerce.service
 * com.liferay.dynamic.data.mapping.service.DDMStructureLocalService for bundle com.liferay.commerce.product.service
 * com.liferay.commerce.account.util.CommerceAccountHelper for bundle com.liferay.commerce.service
 * com.liferay.commerce.product.service.CPDefinitionLocalService for bundle com.liferay.commerce.price.list.service
 * com.liferay.commerce.service.CommerceShippingMethodService for bundle com.liferay.commerce.shipping.engine.fixed.service
 * com.liferay.commerce.tax.engine.fixed.service.CommerceTaxFixedRateAddressRelLocalService for bundle com.liferay.commerce.service
 * com.liferay.commerce.product.permission.CommerceProductViewPermission for bundle com.liferay.commerce.service
 * com.liferay.commerce.price.CommerceOrderPriceCalculationFactory for bundle com.liferay.commerce.service
 * com.liferay.commerce.product.option.CommerceOptionValueHelper for bundle com.liferay.commerce.service
 * com.liferay.commerce.discount.service.CommerceDiscountUsageEntryLocalService for bundle com.liferay.commerce.service
g!

However, this is the one that gets my attention, and which I think causes the rest of the problems:

 * com.liferay.portal.kernel.model.Release (&amp;(release.bundle.symbolic.name=com.liferay.document.library.service)(&amp;(release.schema.version&gt;=3.1.0)(!(release.schema.version&gt;=4.0.0)))(|(!(release.state=*))(release.state=0))) for bundle com.liferay.document.library.service

If I run `ds:unsatisfied` I get a myriad of unsatisfied component references...so I won't paste its output.

The upgrade process for com.liferay.document.library.service displays the following:

g! upgrade:list com.liferay.document.library.service
Registered upgrade processes for com.liferay.document.library.service 3.1.0
        {fromSchemaVersionString=0.0.0, toSchemaVersionString=3.1.0, upgradeStep=Initial Database Creation}
        {fromSchemaVersionString=0.0.1, toSchemaVersionString=1.0.0, upgradeStep=com.liferay.document.library.internal.upgrade.v1_0_0.UpgradeDocumentLibrary@6765c774}
        {fromSchemaVersionString=1.0.0, toSchemaVersionString=1.0.1, upgradeStep=com.liferay.document.library.internal.upgrade.v1_0_2.UpgradeDLFileShortcut@3101094f}
        {fromSchemaVersionString=1.0.1, toSchemaVersionString=1.0.2.step-1, upgradeStep=com.liferay.document.library.internal.upgrade.v1_0_1.UpgradeDLConfiguration@48b71963}
        {fromSchemaVersionString=1.0.2, toSchemaVersionString=1.1.0, upgradeStep=com.liferay.document.library.internal.upgrade.v1_1_0.UpgradeSchema@53846c71}
        {fromSchemaVersionString=1.0.2.step-1, toSchemaVersionString=1.0.2, upgradeStep=com.liferay.document.library.internal.upgrade.v1_0_1.UpgradeDLFileEntryConfiguration@1a135f12}
        {fromSchemaVersionString=1.1.0, toSchemaVersionString=1.1.1, upgradeStep=com.liferay.portal.kernel.upgrade.DummyUpgradeStep@2361766e}
        {fromSchemaVersionString=1.1.1, toSchemaVersionString=1.1.2, upgradeStep=com.liferay.document.library.internal.upgrade.v1_1_2.UpgradeDLFileEntryType@536d1f60}
        {fromSchemaVersionString=1.1.2, toSchemaVersionString=2.0.0, upgradeStep=com.liferay.document.library.internal.upgrade.v2_0_0.UpgradeCompanyId@23fa0698}
        {fromSchemaVersionString=2.0.0, toSchemaVersionString=3.0.0, upgradeStep=com.liferay.portal.kernel.upgrade.UpgradeViewCount@2311363a}
        {fromSchemaVersionString=3.0.0, toSchemaVersionString=3.0.1, upgradeStep=com.liferay.comment.upgrade.UpgradeDiscussionSubscriptionClassName@b6bf630}
        {fromSchemaVersionString=3.0.1, toSchemaVersionString=3.1.0.step-1, upgradeStep=com.liferay.document.library.internal.upgrade.DLServiceUpgrade$1@30467e22}
        {fromSchemaVersionString=3.1.0.step-1, toSchemaVersionString=3.1.0, upgradeStep=com.liferay.portal.kernel.upgrade.UpgradeCTModel@43fb6074}
g!

And a good question could be: is there a way to show the same for the verify process of com.liferay.document.library.service? The GoGo console shows this:

g! verify:check com.liferay.document.library.service
No verify process with name com.liferay.document.library.service
g!

So that's really odd...how come the verify process failed if there's not even one for it?

Many thanks beforehand to anyone giving some feedback

database upgrade framework

Enrique Valdes Lacasa, modified 4 Years ago.

RE: Upgrade from 6.2 CE to 7.3 CE succeeds but OSGi services go missing

Junior Member Posts: 92 Join Date: 7/29/14 Recent Posts

If it's of any help, the start up log is the following:

12-Nov-2020 21:43:41.466 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [1743] milliseconds
Loading jar:file:/C:/work/AoC/bundles/aoc-portal/bundles/tomcat-9.0.37/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/system.properties
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.liferay.petra.reflect.ReflectionUtil (file:/C:/work/AoC/bundles/aoc-portal/bundles/tomcat-9.0.37/lib/ext/com.liferay.petra.reflect.jar) to method java.lang.Object.clone()
WARNING: Please consider reporting this to the maintainers of com.liferay.petra.reflect.ReflectionUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
2020-11-12 21:43:45 JRebel: Monitoring Log4j configuration in 'file:/C:/work/AoC/bundles/aoc-portal/bundles/tomcat-9.0.37/webapps/ROOT/WEB-INF/classes/log4j.properties'.
Loading jar:file:/C:/work/AoC/bundles/aoc-portal/bundles/tomcat-9.0.37/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/portal.properties
Loading file:/C:/work/AoC/bundles/aoc-portal/bundles/portal-ext.properties
Loading file:/C:/work/AoC/bundles/aoc-portal/bundles/tomcat-9.0.37/webapps/ROOT/WEB-INF/classes/portal-developer.properties
2020-11-12 21:43:46.930 INFO  [main][PortalContextLoaderListener:139] JVM arguments: -agentlib:jdwp=transport=dt_socket,address=127.0.0.1:62793,suspend=y,server=n -Drebel.base=C:\Users\evaldeslacasa\.jrebel -Drebel.env.ide.plugin.version=2020.3.0 -Drebel.env.ide.version=2020.2.2 -Drebel.env.ide.product=IU -Drebel.env.ide=intellij -Drebel.notification.url=http://localhost:17434 -Xshare:off -agentpath:C:\Users\evaldeslacasa\AppData\Roaming\JetBrains\IntelliJIdea2020.2\plugins\jr-ide-idea\lib\jrebel6\lib\jrebel64.dll -Dcatalina.base=C:\work\AoC\bundles\aoc-portal\bundles\tomcat-9.0.37 -Dcatalina.home=C:\work\AoC\bundles\aoc-portal\bundles\tomcat-9.0.37 -Dfile.encoding=UTF8 -Djava.io.tmpdir=C:\work\AoC\bundles\aoc-portal\bundles\tomcat-9.0.37\temp -Djava.net.preferIPv4Stack=true -Djava.util.logging.config.file=C:\work\AoC\bundles\aoc-portal\bundles\tomcat-9.0.37\conf\logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false -Duser.timezone=GMT -Xmx4096m -Xms4096m -Dfile.encoding=UTF-8
2020-11-12 21:43:51.543 INFO  [main][DialectDetector:159] Using dialect org.hibernate.dialect.MySQLDialect for MySQL 5.7
2020-11-12 21:43:59.445 INFO  [main][ModuleFrameworkImpl:1595] Starting initial bundles
2020-11-12 21:44:03.866 INFO  [main][ModuleFrameworkImpl:1879] Started initial bundles
2020-11-12 21:44:03.867 INFO  [main][ModuleFrameworkImpl:1932] Starting dynamic bundles
2020-11-12 21:44:11 JRebel: Monitoring Log4j configuration in 'file:/C:/work/AoC/bundles/aoc-portal/bundles/tomcat-9.0.37/webapps/ROOT/WEB-INF/classes/log4j.properties'.
2020-11-12 21:44:34.415 INFO  [main][ModuleFrameworkImpl:1954] Started dynamic bundles
2020-11-12 21:44:34.418 INFO  [main][ModuleFrameworkImpl:1961] Starting web bundles
2020-11-12 21:44:39.827 INFO  [main][ModuleFrameworkImpl:2015] Started web bundles
2020-11-12 21:44:39.828 INFO  [main][ModuleFrameworkImpl:407] Navigate to Control Panel &gt; Configuration &gt; Gogo Shell and enter "lb" to see all bundles
2020-11-12 21:44:40.609 INFO  [main][LoggingTimer:83] Starting com.liferay.portal.events.StartupHelperUtil#initResourceActions
2020-11-12 21:44:40.920 INFO  [main][LoggingTimer:44] Completed com.liferay.portal.events.StartupHelperUtil#initResourceActions in 311 ms
2020-11-12 21:44:47.954 WARN  [main][SidecarManager:109] Liferay automatically starts a child process of Elasticsearch named sidecar for convenient development and demonstration purposes. Do NOT use sidecar in production. Refer to the documentation for details on the limitations of sidecar and instructions on configuring a remote Elasticsearch connection in the Control Panel.
2020-11-12 21:45:13.735 INFO  [main][Sidecar:116] Sidecar Elasticsearch liferay started at 127.0.0.1:9201

    __    ____________________  _____  __
   / /   /  _/ ____/ ____/ __ \/   \ \/ /
  / /    / // /_  / __/ / /_/ / /| |\  /
 / /____/ // __/ / /___/ _, _/ ___ |/ /
/_____/___/_/   /_____/_/ |_/_/  |_/_/

Starting Liferay Community Edition Portal 7.3.5 CE GA6 (Athanasius / Build 7305 / September 22, 2020)

2020-11-12 21:45:48.587 INFO  [main][StartupHelperUtil:107] There are no patches installed
2020-11-12 21:45:50.649 INFO  [main][AutoDeployDir:205] Auto deploy scanner started for C:\work\AoC\bundles\aoc-portal\bundles\deploy
2020-11-12 21:46:03.066 INFO  [main][SystemCheckOSGiCommands:59] System check is enabled. You can run a system check with the command "system:check" in Gogo shell.
2020-11-12 21:46:03.070 INFO  [main][SystemCheckOSGiCommands:71] Running system check
2020-11-12 21:46:03.072 INFO  [main][SystemCheckOSGiCommands:98] Available checkers :[Declarative Service Soft Circular Dependency Checker, Declarative Service Unsatisfied Component Checker, Spring Extender Unavailable Component Checker]
2020-11-12 21:46:03.073 INFO  [main][SystemCheckOSGiCommands:114] Running "Declarative Service Soft Circular Dependency Checker". You can run this by itself with command "ds:softCircularDependency" in gogo shell.
2020-11-12 21:46:10.505 INFO  [main][SystemCheckOSGiCommands:126] Declarative Service Soft Circular Dependency Checker check result: No issues were found.
2020-11-12 21:46:10.505 INFO  [main][SystemCheckOSGiCommands:114] Running "Declarative Service Unsatisfied Component Checker". You can run this by itself with command "ds:unsatisfied" in gogo shell.
2020-11-12 21:46:14.251 INFO  [com.liferay.portal.osgi.web.wab.extender.internal.WabFactory-BundleTrackerOpener][ThemeHotDeployListener:108] 1 theme for classic-theme is available for use
2020-11-12 21:46:14.648 INFO  [com.liferay.portal.osgi.web.wab.extender.internal.WabFactory-BundleTrackerOpener][ThemeHotDeployListener:108] 1 theme for minium-theme is available for use
2020-11-12 21:46:14.987 INFO  [com.liferay.portal.osgi.web.wab.extender.internal.WabFactory-BundleTrackerOpener][ThemeHotDeployListener:108] 1 theme for admin-theme is available for use
2020-11-12 21:46:15.279 INFO  [com.liferay.portal.osgi.web.wab.extender.internal.WabFactory-BundleTrackerOpener][ThemeHotDeployListener:108] 1 theme for speedwell-theme is available for use
2020-11-12 21:46:35.644 WARN  [main][SystemCheckOSGiCommands:137] Declarative Service Unsatisfied Component Checker check result: _Bundle {id: 1441, name: com.liferay.adaptive.media.blogs.web, version: 4.0.9}_	Declarative Service {id: 20, name: com.liferay.adaptive.media.blogs.web.internal.exportimport.content.processor.AMBlogsEntryExportImportContentProcessor, unsatisfied references: _		{name: _blogsEntryExportImportContentProcessor, target: (&amp;(model.class.name=com.liferay.blogs.model.BlogsEntry)(!(component.name=com.liferay.adaptive.media.blogs.web.internal.exportimport.content.processor.AMBlogsEntryExportImportContentProcessor)))}_	}_Bundle {id: 1452, name: com.liferay.adaptive.media.image.item.selector.impl, version: 4.0.6}_	Declarative Service {id: 57, name: com.liferay.adaptive.media.image.item.selector.internal.FileEntryAMImageURLItemSelectorReturnTypeResolver, unsatisfied references: _		{name: _dlURLHelper, target: null}_	}_	Declarative Service {id: 56, name: com.liferay.adaptive.media.image.item.selector.internal.FileEntryAMImageFileEntryItemSelectorReturnTypeResolver, unsatisfied references: _		{name: _dlURLHelper, target: null}_	}_Bundle {id: 1458, name: com.liferay.adaptive.media.journal.web, version: 4.0.7}_	Declarative Service {id: 70, name: com.liferay.adaptive.media.journal.web.internal.transformer.AMJournalTransformerListener, unsatisfied references: _		{name: _journalContent, target: null}_	}_	Declarative Service {id: 69, name: com.liferay.adaptive.media.journal.web.internal.messaging.AMJournalImageConfigurationMessageListener, unsatisfied references: _		{name: _journalContent, target: null}_	}_	Declarative Service {id: 68, name: com.liferay.adaptive.media.journal.web.internal.exportimport.content.processor

And the unsatisfied dependencies log continues waaaaaay down (I couldn't paste it all).

Thanks again!

Enrique Valdes Lacasa, modified 4 Years ago.

RE: Upgrade from 6.2 CE to 7.3 CE succeeds but OSGi services go missing

Junior Member Posts: 92 Join Date: 7/29/14 Recent Posts

Hello everyone.

We were finally able to overcome the issues.

The first problem was that we were not configuring the document library folder properly using the file:

com.liferay.portal.store.file.system.configuration.AdvancedFileSystemStoreConfiguration.config

which can be found in the osgi/configs folder. We needed to set the directory of the document library there using:

rootDir=${document-library-directory}

In portal-upgrade-ext.properties, make sure that you use:

dl.store.impl=com.liferay.portal.store.file.system.AdvancedFileSystemStore

After this, if you notice in the first log I posted, there is a NoSuchFileVersionException. This was happening because a given DLFileEntry had been kept in the database but for some reason it didn't have an associated DLFileVersion record (plus other metadata records were missing as well). So this file entry was wrong and the upgrade process complained about it. Once I manually removed the isolated file entry from the DLFileEntry table, the ugprade went well and we didn't get any issues with services.

Community

Company

Feedback

Ask Questions and Find Answers

Important:

Ask is now read-only. You can review any existing questions and answers, but not add anything new.

But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:

discuss.liferay.com

Upgrade from 6.2 CE to 7.3 CE succeeds but OSGi services go missing