Liferay Patching Overview

The Liferay Support Team creates and releases fixes to address product defects. These are released as zipped patch files, zipped bundled updates and deployable war files.

Patch files can be installed by utilizing the Patching Tool which is included in every Liferay bundle.  More information on installing patches may be found here:

Bundles can be expanded and installed in the desired environment or used as part of a scripted deployment process. More information on installing bundles may be found here:

The Release Notes Tool that makes it easy to compare all of the changes between different DXP releases, updates, or fix packs including module version changes.  This is helpful in planning upgrades and identifying any potential impact to your customizations.

Patch Releases, Updates, Fix Packs, and Services Packs can be downloaded from our Downloads page. With each type of release, release notes are provided outlining important information, such as breaking changes, security fixes, and a changelog with detailed information for each fix. Hotfixes are not listed for public download. Hotfixes will be attached to customer tickets or can be requested through Liferay Support.

Liferay delivers fixes through these three types of releases:

Patch Releases

A Patch Release is a cumulative bundled release of a Quarterly Release which contains new fixes and all the fixes and features from previous updates. Patch Releases should not contain new features but only the features previously released in a Quarterly Release.

All Patch Releases are built from source and bundled together with the most up-to-date:

  1. Patching Tool
  2. Tomcat Application server
  3. Latest fixes for the Quarterly Release


An update is a cumulative bundled release which contains new fixes and all the fixes and features from previous updates. Updates may also contain new features depending on the version.

  • Updates for DXP 7.4 contain the latest fixes and new features bundled together.
  • Updates for DXP 7.3 contain the latest fixes and select new features bundled together.

All Updates are built from source and bundled together with the most up-to-date:

  1. Patching Tool
  2. Tomcat Application server
  3. Latest DXP Update level
  4. Bundled Marketplace Apps

Fix Pack

A Fix Pack is a collection of the latest fixes bundled together. Fix Packs are cumulative and contain all the fixes from previous Fix Packs. 

Fix packs are released as a zipped patch file and can be downloaded from our Downloads page.  With each Fix Pack, release notes are provided outlining important information, such as Important Changes, security fixes, and a changelog with more detailed information for each fix.


In cases when you encounter an issue which is not yet addressed in a Fix Pack, you can create a Help Center ticket to request a Hotfix. Liferay Support will work together with you to determine if the issue is with the product, and provide a fix for any unintended behavior.

There are two types of hotfixes, standard and cumulative (see below). The Liferay version you are on determines the type of hotfix you will receive (Standard for DXP, Cumulative for Portal EE). These hotfixes are not publicly available for download, you need to contact our Liferay Support Team to obtain them. Hotfixes are installed with the Patching Tool and are specific to the individual customer. Applying hotfixes from other customers may lead to conflicts and create further issues. Hotfixes are available for gold and platinum customers.

Standard Hotfix
(For versions DXP 7.0+)

Standard hotfixes are built assuming a specific Fix Pack level, and must be installed with the corresponding Fix Pack present in the Patches folder. At any given moment one hotfix and one fixpack may be installed together.  A standard hotfix may contain more than one fix and even a complete Fix Pack if necessary.

Cumulative Hotfix
(For version Portal 6.2 EE)

For Portal 6.2 EE, when a hotfix is created, all your currently installed Fix Packs are included in the hotfix. These hotfixes cannot be installed together with Fix Packs.

Note: Our engineers will need to know which patches are installed on your system. When you contact Liferay Support requesting a hotfix please share this information as it is essential to build a Hotfix. With the Patching Tool you can easily create a text file which contains all the necessary details using the support-info command.

Security Fixes

A security issue may be fixed with a hotifx, a security fix, or a fix pack.  For DXP, security issues please see: DXP Security Fix Packs

For Portal 6.2 EE, security issues may be temporarily fixed with a hotfix.  Security fixes are then released and delivered to all Portal 6.2 EE customers in the next Fix Pack release. This Fix Pack will include the latest security fixes along with other fixes, as well.

If you are not planning to install all of the latest Fix Packs (or Security Fix Packs) but still need the security fix, please create a Help Center ticket to request a hotfix.

Service Packs

Periodically, the latest fixes and Fix Packs are merged together into a Service Pack. Service Packs are built from source and bundled together with the most up-to-date:

  1. Patching Tool
  2. Fix Pack 
  3. Bundled Marketplace Apps
  4. Tomcat Application server

Service Packs can be downloaded from our Downloads page. Service Packs are cumulative and contain all the fixes from previous Fix Packs and Service Packs.  For existing installations, please follow the instructions on updating to the latest Service Pack level, here: 

Note: In previous versions of Liferay Portal (6.0.12, 6.1.10, 6.1.20) the Fix Packs were not compatible with different Service Packs, they can only be installed by rebuilding the portal environment from the new bundles. Fix Packs were only compatible with one Service Pack (or GA as they were called in 6.1 EE) so they couldn't be installed on other versions.



How Patches are Tested

Liferay extensively tests all types of releases to ensure high quality. Fix Packs and Updates go through both automated regression testing and manual testing. Hotfixes receive similar automated testing, and the fix for the reported issue is tested by the support engineer who built the fix and the support engineer assigned to the Help Center ticket.

Before releasing a bundle such as Service Pack or Update, additional test suites run on the packaged releases to ensure the quality of the packaging.

Conflicts Between Fix Packs and Hotfixes

A conflict happens when a fix modifies the same file which has already been modified by a Fix Pack. The Patching Tool is not able to decide how to handle these so the case has to be verified and resolved by an engineer (sometimes the logic has to be adjusted as well). This is called a merge because the new fix has to include the previous one as well. The Patching Tool looks for information in the patches so it knows how to install the various patches correctly.

Previously with standard hotfixes, many combinations of conflicts emerged and needed to be handled which lead to slower and more error prone resolutions. Also, every customer could have a completely different environment.

By releasing fix packs more often the need to handle these conflicts occurs only once in the newer fix pack. This way we can reduce the number of different environments our customers may have. From versions 6.1.30 and 6.2.10 ideally only the fix packs are used in a Liferay installation. In case there is an urgent need to handle a malfunction a cumulative hotfix can be requested. After releasing and installing a cumulative hotfix there is still a possibility to go back to use fix packs if the fix is included in a fix pack later on.

Important: Make sure to backup your Liferay DXP installation and database regularly, especially before patching. The patching tool installs code changes and some of these make data changes (if necessary) automatically on startup.

Certain fix packs (service packs) can include data/schema micro changes—they’re optional and revertible. Module upgrades and any micro changes they include are applied at server startup by default, or can be applied manually by disabling theautoUpgradeproperty. Server startup skips all Core micro changes. Instead, you can apply them using the upgrade tool before server startup.

Additional Information

Was this article helpful?
1 out of 1 found this helpful