Deployment startup up error liferay 7.4.3.26 GA27 Wildfly 23

RE: RE: Deployment startup up error liferay 7.4.3.26 GA27 Wildfly 23

2022-06-15T18:20:23Z

Thanks Olaf, our use case is that we have monthly/on demand scans from Sonatype, Webinspect and Fortify. Whenever there is a critical vulnerabilty we need to remediate in 30 days. Some of the liferay GA releases addresses these issues. So we looking ways how to install/upgrade theses GA releases easliy. I am big believer in stick with the current releases for sometime and then upgrade. However, due this policy from security team to update these libraries its become top priority.

However, just to summarize what you said so I understand see below

1. Liferay Workspace provides a couple of targets for different environments to build for - Do I update these target workspaces in the gradle.properties with the new GA releaese? How would this address extracting the WAR, OSGI files?

2. You could build docker images and always point them to the same database/filestore/search server. I am currently looking at this approach as it may fit my use case. After reading the instructions ont he docker upgrade it seems just and update to GA image relase and thats is wala :). Is there a detail documentation on how to use the docker image in liferay? Will this be a better approach for my Use case as describe above?

3. Best to completely replace (make sure not just to overwrite, as it might leave old code around wreaking havoc). I have been maually removing the contents from the ROOT.war leaving it empty and replacing it with the new GA war file in that ROOT.war folder. Are you saying for option 1 or option2 to completely remove the contents of ROOT.war before pulling an image or installing the WAR file manually?

Hope my questions make sense and I am following you correctly :)

Thanks,

Kevin

RE: RE: Deployment startup up error liferay 7.4.3.26 GA27 Wildfly 23

2022-06-15T15:03:01Z

Just the WAR replacement won't do it. The WAR contents go together with the OSGi libraries.

Liferay Workspace provides a couple of targets for different environments to build for, you could build docker images and always point them to the same database/filestore/search server. Either way: Best to completely replace (make sure not just to overwrite, as it might leave old code around wreaking havoc)

There's no need to do this every week (for every release), but I'd recommend to stay in shape and with a current version. If you're used to upgrades, they'll be quick, small and easy.

Was it Martin Fowler, or somebody else, who said: "If it hurts, you'll need to do it more often". This is the current principle. Not too much is different from week to week.

RE: RE: Deployment startup up error liferay 7.4.3.26 GA27 Wildfly 23

2022-06-14T19:52:16Z

Hi Jorge, Thanks :). I have it running now with G28 release . But I noitce that I cant replace G28 war file with G27 osgi and toolls folders as I will get errors as shown in my last comment. I have a question, with these vulnerabilites we have to constantly upgrade to the next GA release. Whats the best practice to do the upgrade ? Can we take the latest GA war file and just replace it in the ROOT.war folder? Or Do we have to do a fresh install with the osgi an tools folder?

Thanks

Kevin

RE: Deployment startup up error liferay 7.4.3.26 GA27 Wildfly 23

2022-06-13T16:40:56Z

This is the same than LPS-155053

It is solved in 7.4 update 28

As a workaround you can configure upgrade.database.auto.run=false and manually upgrade using the upgrade tool.

Deployment startup up error liferay 7.4.3.26 GA27 Wildfly 23

2022-06-13T15:42:35Z

Hello, when i install liferay 7.4.3.26 WAR to ROOT.war folder and start the the server I get a deoployment failure message as hown below in my ROOT.war.failed file. Does anyone know what could be causing this error? I am running on Wildfly 23.

"{\"WFLYCTL0080: Failed services\" => {\"jboss.deployment.unit.\\\"ROOT.war\\\".undertow-deployment\" => \"java.lang.RuntimeException: java.lang.reflect.UndeclaredThrowableException
Caused by: java.lang.RuntimeException: java.lang.reflect.UndeclaredThrowableException
Caused by: java.lang.reflect.UndeclaredThrowableException
Caused by: java.lang.reflect.InvocationTargetException
Caused by: java.lang.RuntimeException: com.liferay.portal.kernel.upgrade.UpgradeException: Store \\\"com.liferay.portal.store.db.DBStore\\\" is not available
Caused by: com.liferay.portal.kernel.upgrade.UpgradeException: Store \\\"com.liferay.portal.store.db.DBStore\\\" is not available\"}}"