Updated Patch Management with EAP 6.2+

Updated -


Starting with EAP 6.2, a JBoss CLI command called patch has been added for the application of both individual and cumulative patches. In addition to this patch installation functionality, maintenance releases of minor versions will change to better accommodate customer expectations.

This article discusses some of the benefits of the new patch management approach that is delivered with Red Hat JBoss EAP 6.2. If you are looking for the specifics of how to use the new tool, please review the section Related articles below.

Definition of Terms

Before we discuss the changes, we need to define the terms we shall be using.

  • Individual Patch
    • An individual patch addresses a single issue and is not not tested in combination with any other patches.
    • Individual patches will be delivered to customers via support cases and then incorporated into the next possible cumulative patch update.
    • The application of multiple individual patches in a single environment may lead to unanticipated product configurations which can lead to unexpected behavior.
  • Cumulative Patch
    • A cumulative patch is a delivery mechanism by which customers can update their existing installations to the most recent patch level without the need for a new installation.
    • A cumulative patch consists of multiple bug and/or security fixes which are tested together.
    • Cumulative patches encompass prior cumulative patches as well, so only the last cumulative patch in a minor release family needs to be applied.
    • Application of a cumulative patch will automatically invalidate previously installed individual patches.
    • Cumulative patches will be made available via the Customer Portal approximately every 6 weeks.
  • RPM
    • RPM is a mature software delivery mechanism
    • All cumulative patch updates will have corresponding RPM updates.
    • RPM updates will be made available via the appropriate minor version RPM channel.


In a similar manner to RPMs, cumulative patches provide the following benefits:

  • Easy installation via tooling
  • Proactive distribution of targeted
    • Bug fixes
    • Security Fixes or
    • Combined bug and security fixes
  • Holistic quality assurance across all changes (cumulative patches are tested as a whole, not in isolation)


To take advantage of these benefits, we recommend applying the latest RPM or cumulative patch updates as regularly as possible. For new installations of EAP, it is recommended that the latest update be applied to the GA release as a part of the installation process.

Exceptional Circumstances

In production deployments, conditions might arise that require the provision of bug and/or security fixes in a timely manner, that does not fit the regular maintenance schedule. In these situations, an individual patch may be provided in accordance with the EAP 6.2+ Individual Patch Policy.

Related articles

How do I apply individual or cumulative patches in JBoss EAP 6.2 and beyond?
How do I verify a patch has been installed in EAP 6.2+?
How do I rollback individual or cumulative patches in JBoss EAP 6.2 and beyond?
The Patch Command and Minor Version Upgrades of JBoss EAP
BAS016840: Patch does not apply - expected (6.3.0.GA), but was (6.3.2.GA)
Unable to Apply JBoss EAP 6 CP When Native Components are Installed
JBoss EAP 6.2.0 size too large after applying patch 6.2.4

JBoss EAP 6 Maintenance Schedule
EAP 6.2+ Individual Patch Policy


It would be great if you could add a download zip for the complete EAP with the latest patch level, e.g. JBoss Enterprise Application Platform 6.4.8