Red Hat Summitこのコンテンツは選択した言語では利用できません。
Chapter 2. Patching Red Hat JBoss Data Grid Server Instances
2.1. Applying Patches to Red Hat JBoss Data Grid Server Instances
Red Hat JBoss Data Grid server uses the patching functionality in JBoss Enterprise Application Platform (EAP) so that you can apply changes from errata releases without the need to completely replace an existing installation.
Patches are distributed for cumulative updates within a release version. The base version for this release is 7.2.0. You can apply 7.2.x patches to the base version or on top of other patches.
You cannot apply 7.2.x patches to any other JBoss Data Grid release version. Likewise you cannot apply patches from other release versions to the 7.2 release.
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.
If you have applied the patch for JBoss Data Grid 7.2.2, you must first revert that patch before you apply the patch for JBoss Data Grid 7.2.3 or later. A known issue exists that prevents you from applying any patch on top of JBoss Data Grid 7.2.2.
To revert the patch for JBoss Data Grid 7.2.2, you do not need to reset the configuration. Revert the patch as follows:
bin/cli.sh "patch rollback --patch-id=jboss-jdg-7.2.2.CP --reset-configuration=false"
$ bin/cli.sh "patch rollback --patch-id=jboss-jdg-7.2.2.CP --reset-configuration=false"See Reverting Patches for information on rolling back patches.
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.
To avoid issues with classloading, you should not apply patches to JBoss Data Grid while the server 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.2.x-server-patch.zip"
$ bin/cli.sh "patch apply /path/to/jboss-datagrid-7.2.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. Reverting Patches
You can roll back patches to revert the Red Hat 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.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}