EAP Patching

External

• Patching a ZIP/Installer Installation https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Installation_Guide/sect-Patching_JBoss_EAP_6.html#sect-Patching_a_ZipInstaller_Installation

Internal

• WildFly Operations
• WildFly Versioning

Relevance

• EAP 6.4

Overview

Patches are distributed as zip files or RPMs (for a subset of products).

Patching with zip files and patching with RPMs is incompatible, the same method should be used for subsequent patches.

After a patch is applied, the patched JARs are picked up at runtime from:

$JBOSS_HOME/modules/system/layers/base/.overlays/$PATCH_ID/$MODULE

while the original files are left in

$JBOSS_HOME/modules/system/layers/base/$MODULE

The patching mechanism renders the original JAR files unusable, for security reasons. If the patch is rolled back, the original files will be reverted to an usable state.

Info

From CLI:

/core-service=patching:ageout-history

Patching in Domain Mode

The patch management system cannot be used to automatically patch server instances across a managed domain: individual server instances in the managed domain must be patched independently.

Procedure

From CLI:

parch apply /path/to/patch.zip
shutdown --restart=true