Liferay Portal 7.4 GA6 and Liferay Commerce 4.0 GA6 Release

We are pleased to announce the release of Liferay Portal 7.4 GA6 and Liferay Commerce 4.0 GA6!

The Liferay Portal 7.4 GA6 release is primarily focused on fixes so no new notable features will be introduced with this release.

Download options

Liferay Portal and Liferay Commerce share the same Bundle and Docker image.  To get started using either Liferay Portal or Liferay Commerce, choose the best download option suited for your environment below.

Docker image

To use Liferay Portal 7.4 GA6:

docker run -it -p 8080:8080 liferay/portal:

For more information on using the official Liferay docker image see the liferay/portal repo on Docker Hub.

Bundles and other download options

If you are used to binary releases, you can find the Liferay Portal 7.4 GA6 and Liferay Commerce 4.0 GA6 release on the download page.  If you need additional files (for example, the source code, or dependency libraries), visit the release page.

Dependency Management

For development using the Liferay Platform, update Liferay Workspace to use the  latest dependencies, by adding the following line to the build.gradle file:

dependencies {
	compileOnly group: "com.liferay.portal", name: "release.portal.api"

All portal dependencies are now defined with a single declaration. When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.  

By setting a product info key property it will be possible to update all dependencies to a new version by updating the liferay.workspace.product property in the liferay workspace projects file:

liferay.workspace.product = portal-7.4-ga6

When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.


All documentation for Liferay Portal and Liferay Commerce can now be found on our documentation site:  For more information on upgrading to Liferay Portal 7.4 GA6 see refer to the Upgrade Overview.

Compatibility Matrix

Liferay's general policy is to test Liferay Portal and Liferay Commerce  against newer major releases of operating systems, open source app servers, browsers, and open source databases (we regularly update the bundled upstream libraries to fix bugs or take advantage of new features in the open source we depend on). 

Liferay Portal 7.4 GA6 and Liferay Commerce 4.0 GA6 were tested extensively for use with the following Application/Database Servers: 

Application Server

  • Tomcat 9.0

  • Wildfly 17.0


  • HSQLDB 2 (only for demonstration, development, and testing)

  • MySQL 5.7, 8.0

  • MariaDB 10.2, 10.4

  • PostgreSQL 12.x, 13.x


  • IBM J9 JDK 8

  • Oracle JDK 8

  • Oracle JDK 11

  • All Java Technical Compatibility Kit (TCK) compliant builds of Java 11 and Java 8

Source Code

Source is available as a zip archive on the release page, or on its home on GitHub. If you're interested in contributing, take a look at our contribution page.

Bug Reporting

If you believe you have encountered a bug in the new release you can report your issue by following the bug reporting instructions.

Getting Support

Support is provided by our awesome community. Please visit helping a developer page for more details on how you can receive support.

Fixes and Known Issues


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": "", "mx": "", "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( ~[portal-impl.jar:?]         at com.liferay.portal.repository.RepositoryFactoryImpl.createLocalRepository( ~[portal-impl.jar:?]         at com.liferay.portal.repository.RepositoryProviderImpl.getLocalRepository( ~[portal-impl.jar:?]         at com.liferay.portlet.documentlibrary.service.impl.DLAppLocalServiceImpl.getLocalRepository( ~[portal-impl.jar:?]         at com.liferay.portlet.documentlibrary.service.impl.DLAppLocalServiceImpl.fetchFileEntryByExternalReferenceCode( ~[portal-impl.jar:?]

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?

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:", 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:", the exception logs will not appear.

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.