Liferay Portal 7.3 CE GA7 Release

We are pleased to announce the release of Liferay Portal CE 7.3 GA7!

The Liferay Portal 7.3 CE GA7 release is primarily focused on fixes so no new notable features will be introduced with this release.  Work continues on Liferay Portal CE 7.4 GA1 so look forward to hearing news soon regarding it's impending release.

Download options

Choose the best download option suited for your environment below.

Docker image

To use Liferay Portal 7.3 CE GA7 in docker, run:

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

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.3 CE GA7 release on the download page.  If you need additional files (for example, the source code, or dependency libraries), visit the release page.

Dependency Management

If you are developing on top of Liferay Platform using Liferay Workspace, you will only need to define a single dependency artifact by adding the following line to each modules build.gradle file:

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

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.3-ga7

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 new documentation site called  For more information on our new documentation initiative see the official announcement here.

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.3 CE and Liferay Commerce 3.0 were tested extensively for use with the following Application/Database Servers: 

Application Server

  • Tomcat 9.0

  • Wildfly 16.0 (Previously 11.0)


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

  • MySQL 5.7, 8.0

  • MariaDB 10.2

  • PostgreSQL 11.2 (Previously 10)


  • 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


The blog system is broken and does not work in this version.

Hi, can you provide some details on what issue you are seeing with blogs?  I tested it and it seems to work fine for me.

Hi, the error is " Blogs is temporarily unavailable" also in admin control panel blogs section, and same error when adding blogs portlets in widget page. I downloaded the 7z bundle version from liferay website. Also i tested in Safari and Chrome. The same error i founded in liferay-portal-tomcat-master-all.7z

Thank you

Hi, can you provide your environment such as OS, Database and JVM version?  I am running on MacOS with JDK 1.8 and it seems to be working for me.  Also can you supply any logs with errors in them?  If it's easier you can post this in which supports attaching logs better.

Oh, that was unexpected...

We thought that Liferay 7.3.5 GA6 was the latest release before 7.4.

What is the best way to upgrade our modules for this "small upgrade" from 7.3.5 GA6?

When we were talking to a Sales Manager of Liferay he advised us to use - if possible - always the "latest CE version before an bigger version change". 

Will we need to go through all the upgrade pain again after upgrading from 7.2 x to 7.3.5? Or is there an easier way for 7.3.5 to 7.3.6?

Best regards

Standard Upgrade procedures. But this time it's meant to be a feature-stable version, so unless you're relying on a bug to be present, or unless you change implementation, the upgrade (especially on code level) should be a recompile at max.Keyword is "should", of course. But that's the basic expectation.

Liferay Module Project Fragments seem to not work anymore.

When creating them from the IDE they can't be deployed - even with no change.  :(


Since I downloaded the new 7.3.6ga7 CE version I cant deploy Liferay Module Project Fragments automatically anymore.

At first I thought they arent working at all anymore like Harry K said.

But it seems that if I deploy a Liferay Module Project Fragment I have to manually refresh the host module. I didnt have to do this in the past so I am very confused why I have to do this now. Can somebody help me?

I already asked in the forum and Russel Bohl came up with the idea of refreshing the host module. Here are some more details of my problem:

Can anybody confirm that they have similar issues?

I just updated a personal project from GA6 to GA7 and found out that my persistence class is no longer working.

javax.portlet.PortletException: java.lang.NullPointerException

at com.liferay.portal.kernel.portlet.bridges.mvc.BaseMVCActionCommand.processAction(

at com.liferay.portal.kernel.portlet.bridges.mvc.MVCPortlet.callActionMethod(

at com.liferay.portal.kernel.portlet.LiferayPortlet.processAction(

at com.liferay.portal.kernel.portlet.bridges.mvc.MVCPortlet.processAction(

at com.liferay.portlet.internal.FilterChainImpl.doFilter(

at com.liferay.portal.kernel.portlet.PortletFilterUtil.doFilter(

at com.liferay.portal.kernel.servlet.PortletServlet.service(

at javax.servlet.http.HttpServlet.service(


Caused by: java.lang.NullPointerException

at com.liferay.portal.cache.internal.dao.orm.FinderCacheImpl._getArguments(

at com.liferay.portal.cache.internal.dao.orm.FinderCacheImpl.updateByEntityCache(

at com.liferay.portal.cache.internal.dao.orm.EntityCacheImpl._putResult(

at com.liferay.portal.cache.internal.dao.orm.EntityCacheImpl.putResult(

at com.liferay.portal.cache.internal.dao.orm.EntityCacheImpl.putResult(

at com.liferay.portal.cache.internal.dao.orm.EntityCacheImpl.putResult(

at com.alg.erp.vendor.service.persistence.impl.VendorContactPersistenceImpl.updateImpl(

at com.alg.erp.vendor.service.persistence.impl.VendorContactPersistenceImpl.updateImpl(

at com.liferay.portal.kernel.service.persistence.impl.BasePersistenceImpl.update(


I use service builder to build my tables and the function is calling: vendorContact = super.addVendorContact(vendorContact);

Figured it out. It looks like my version of Blade was old and workspace as well.  So these functions worked fine in 7.3 ga6, but  needed to recompile with GA7.