gavin lau 2 Years Ago I ran it in the docker get the error: 2022-01-10 12:52:36.677 WARN [Portal Dependency Manager Component Executor--1][PortalInstanceLifecycleListenerManagerImpl:162] Unable to register portal instance {"mvccVersion": 1, "companyId": 20099, "userId": 0, "userName": "", "createDate": "Mon Dec 27 22:40:19 GMT 2021", "modifiedDate": "Mon Dec 27 22:40:19 GMT 2021", "webId": "liferay.com", "mx": "liferay.com", "homeURL": "", "logoId": 0, "system": false, "maxUsers": 0, "active": true, "name": "Liferay", "legalName": "", "legalId": "", "legalType": "", "sicCode": "", "tickerSymbol": "", "industry": "", "type": "", "size": ""} com.liferay.portal.kernel.repository.UndeployedExternalRepositoryException: Unable to load external repository class com.liferay.portal.repository.liferayrepository.LiferayRepository because its plugin is not deployed at com.liferay.portal.repository.RepositoryFactoryImpl.getRepositoryFactory(RepositoryFactoryImpl.java:72) ~[portal-impl.jar:?] at com.liferay.portal.repository.RepositoryFactoryImpl.createLocalRepository(RepositoryFactoryImpl.java:39) ~[portal-impl.jar:?] at com.liferay.portal.repository.RepositoryProviderImpl.getLocalRepository(RepositoryProviderImpl.java:268) ~[portal-impl.jar:?] at com.liferay.portlet.documentlibrary.service.impl.DLAppLocalServiceImpl.getLocalRepository(DLAppLocalServiceImpl.java:1769) ~[portal-impl.jar:?] at com.liferay.portlet.documentlibrary.service.impl.DLAppLocalServiceImpl.fetchFileEntryByExternalReferenceCode(DLAppLocalServiceImpl.java:691) ~[portal-impl.jar:?] Please sign in to reply. Reply as... Cancel Jamie Sammons gavin lau 2 Years Ago Hi Gavin, I tried it locally and it worked fine for me. It seems to be having an issue with creating a local data directory. Are you trying to map a data volume and maybe something is going on with that? Please sign in to reply. Reply as... Cancel Niles Wu Jamie Sammons 2 Years Ago - Edited Hi, Jamie, your are right ! If I use "docker run -it -m 8g --name liferay-lab-74ga7 -v D:\developer\platform\liferay-portal-7.4-ga7:/mnt/liferay -p 8080:8080 liferay/portal:7.4.3.7-ga7", the exception logs will appear. But the application still work normally. If I only use "docker run -it -m 8g --name liferay-lab2-74ga7 -p 8080:8080 liferay/portal:7.4.3.7-ga7", the exception logs will not appear. Please sign in to reply. Reply as... Cancel
Jamie Sammons gavin lau 2 Years Ago Hi Gavin, I tried it locally and it worked fine for me. It seems to be having an issue with creating a local data directory. Are you trying to map a data volume and maybe something is going on with that? Please sign in to reply. Reply as... Cancel Niles Wu Jamie Sammons 2 Years Ago - Edited Hi, Jamie, your are right ! If I use "docker run -it -m 8g --name liferay-lab-74ga7 -v D:\developer\platform\liferay-portal-7.4-ga7:/mnt/liferay -p 8080:8080 liferay/portal:7.4.3.7-ga7", the exception logs will appear. But the application still work normally. If I only use "docker run -it -m 8g --name liferay-lab2-74ga7 -p 8080:8080 liferay/portal:7.4.3.7-ga7", the exception logs will not appear. Please sign in to reply. Reply as... Cancel
Niles Wu Jamie Sammons 2 Years Ago - Edited Hi, Jamie, your are right ! If I use "docker run -it -m 8g --name liferay-lab-74ga7 -v D:\developer\platform\liferay-portal-7.4-ga7:/mnt/liferay -p 8080:8080 liferay/portal:7.4.3.7-ga7", the exception logs will appear. But the application still work normally. If I only use "docker run -it -m 8g --name liferay-lab2-74ga7 -p 8080:8080 liferay/portal:7.4.3.7-ga7", the exception logs will not appear. Please sign in to reply. Reply as... Cancel
Jan Tošovský 2 Years Ago - Edited Would it be possible to explain the current release cadency in a dedicated blog post? Is it new standard or just a must because of mitigation of Lo4J issues? Thanks. Please sign in to reply. Reply as... Cancel Jamie Sammons Jan Tošovský 2 Years Ago Hi Jan, I will work on creating a post detailing the new release cadence. In short it is not related to the Log4j issue and is related to our new release strategy. Please sign in to reply. Reply as... Cancel
Jamie Sammons Jan Tošovský 2 Years Ago Hi Jan, I will work on creating a post detailing the new release cadence. In short it is not related to the Log4j issue and is related to our new release strategy. Please sign in to reply. Reply as... Cancel