Este conteúdo não está disponível no idioma selecionado.
Chapter 2. Applying Patches to JBoss Data Grid
2.1. Patching Existing Server Instances Copiar o linkLink copiado para a área de transferência!
Micro releases for the JBoss Data Grid server are distributed as a patch. This is for your convenience, as the new version will not completely replace the installation. The base version to be patched is the x.y.0 release, and the patches x.y.# (micro release or cumulative patch) may be applied to that instance. The patch can be rolled back (including the configuration) if there is any issue during the patching process, and any subsequent patches may be applied in the same way.
JBoss Data Grid provides patches for server instances only (Remote Client-Server mode). All other distributions, such as EAP modules, clients, and JBoss Data Grid Library mode, are provided as full releases.
To avoid issues with classloading, you should not apply patches to JBoss Data Grid while the server is running.
To apply a patch to JBoss Data Grid, do the following:
- Download the patch from the Red Hat Customer Portal at https://access.redhat.com/downloads/
 Stop the server instance that you want to patch if it is running.
Either use the Administration Console to stop the server or enter Ctrl-C in the terminal where JBoss Data Grid is running.
Open a terminal and change to the JDG_HOME directory.
cd JDG_HOME
$ cd JDG_HOMECopy to Clipboard Copied! Toggle word wrap Toggle overflow Apply the patch as follows:
bin/cli.sh "patch apply /path/to/jboss-datagrid-7.1.x-server-patch.zip"
$ bin/cli.sh "patch apply /path/to/jboss-datagrid-7.1.x-server-patch.zip"Copy to Clipboard Copied! Toggle word wrap Toggle overflow Start the server with either the standalone.sh or domain.sh script, for example:
bin/standalone.sh -c clustered.xml
bin/standalone.sh -c clustered.xmlCopy to Clipboard Copied! Toggle word wrap Toggle overflow 
2.2. Rolling Back the Server Version Copiar o linkLink copiado para a área de transferência!
You can roll back patches to revert the JBoss Data Grid server to the previously installed version.
You should roll back patches only after applying a patch that results in unexpected behavior or undesirable effects. Rolling back patches is not intended for general uninstall functionality.
To revert a JBoss Data Grid patch, do the following:
Stop the server instance that you want to roll back if it is running.
Either use the Administration Console to stop the server or enter Ctrl-C in the terminal where JBoss Data Grid is running.
Open a terminal and change to the JDG_HOME directory.
cd JDG_HOME
$ cd JDG_HOMECopy to Clipboard Copied! Toggle word wrap Toggle overflow Find the ID of the patch that you want to roll back.
bin/cli.sh "patch history"
$ bin/cli.sh "patch history"Copy to Clipboard Copied! Toggle word wrap Toggle overflow Roll back the server version as follows:
bin/cli.sh "patch rollback --patch-id=PATCH_ID --reset-configuration=false"
$ bin/cli.sh "patch rollback --patch-id=PATCH_ID --reset-configuration=false"Copy to Clipboard Copied! Toggle word wrap Toggle overflow WarningUse caution when specifying the
reset-configurationoption.--reset-configuration=falsedoes not revert the server configuration. Because applying patches can change the server configuration, it is possible that the server does not restart if you roll back the patch but do not roll back the configuration. In this case, you should verify the server configuration and manually adjust it as needed before starting the server.--reset-configuration=truereverts the server configuration to the pre-patch state. Any changes to the server configuration after the patch was applied are removed.If conflicts exist when you attempt to roll back the patch, the operation fails and warnings occur. Enter
patch --helpto list available arguments that you can use to resolve the conflicts.- Start the server with either the standalone.sh or domain.sh script.