Release Notes
Patch ID - 5315_20200420
This is a cumulative/rollup patch for CM1 5.3 SR1. This is a minor patch that contains updates to resolve several patch installation issues on Linux servers.
An updated list of Known Issues can be found at the bottom of this page.
For details on bug fixes and improvements in previous patch updates, please see the release notes for prior patches. Links to prior patch release notes are provided below:
- 5315_20200410
- 5315_20200310
- 5315_20191105
- 5315_20191021
- 5315_20190901
- 5315_20190810
- 5315_20190704
- 5315_20190524
- 5315_20190520
- 5315_20190326
- 5315_20190220
- 5315_20181210
- 5315_20181017
- 5315_20180816
- 5315_20180621
- 5315_20180523
- 5315_20180501
- 5315_20180409
- 5315_20180405
- 5315_20180315
- 5315_20180306
- 5315_20180301
- 5315_20180125
- 5315_20180105
- 5315_20171120
- 5315_20170606
- 5315_20170317
- 5315_20161102
ISSUES ADDRESSED IN THIS PATCH:
- [CMS-6631] - Installing 5315_20200410 patch after uninstalling 5315_20200310 patch fails on Linux
- [CMS-6632] - CM1 service fails to start on Linux after applying 5315_20200410 patch - SiteImprove fails to install - Maintenance Error screen displayed
- [CMS-6641] - DTS Metadata Service Fails to start after patching due to missing Derby JDBC Driver errors.
- [CMS-6642] - Spring Errors on CM1 Startup after applying 5.3 patch on fresh install of 5.3
INSTALLATION NOTES & COMMON ISSUES
MEMORY REQUIREMENTS
Patch updates include additional caches that can increase the minimum memory requirements from 2GB to 4GB. Verify that the memory setting in PercussionServer.lax file is set to at least a value of -xmX 4096m when patching to avoid unexpected outages due to out of memory errors.
DATABASE UPDATES
Beginning with Patch 5315_20181221 the update engine now supports database schema updates as part of the update process. As a result the patch relies on the installer database configuration file to successfully run. In environments where the database setup has changed, or a server / RDBMS migration has occurred, it is possible that the installation database configuration file may be out of date which would cause the patch to fail. To avoid this problem, prior to installing the Patch verify that the contents of the <InstallDir>/rxconfig/Installer/rxrepository.properties file are correct. Updating this file is covered in the Appendix A section of the Migrating Percussion Environments help page.
COMMON ISSUES / WORKAROUNDS
Updates can occasionally fail to apply for a variety of reasons. To help streamline troubleshooting, we have created a new Common Issues / Workarounds page to collect the steps to correct these issues if you run into them when patching. As always if you run into a problem applying a patch, please contact the Technical Support team at percussion.support@intsof.com, and they will be happy to assist.
CMS-5294 - The Ignore Unmodified Assets publishing feature does not work correctly on systems with 2000 or more Assets. We recommend that this option be unchecked in your publishing configuration to avoid publishing failures.
- CMS-3614 - After applying the patch end users may need to clear their browser cache in the CM1 user interface in order to see the new changes to the Rich text Editor and plugins.
- CMS-3257 - Customers using the MySQL database server as the backing database for the DTS, will lose the MySQL Connector jar if it was previously placed into the <InstallDir>/Deployment/Server/perc-lib directory. To correct this problem the MySQL Connector for Java may be installed or symlinked into the <InstallDir>/Deployment/Server/lib directory. Percussion does not include this connector as part of our installation due to license incompatibility issues.
- CMS-3490 - Customers patching the DTS on Windows Servers will need to reinstall the DTS Windows service by using the "<InstallDir>\Deployment\Server\bin\service.bat remove" and "<InstallDir>\Deployment\Server\bin\service.bat install" commands. Once the service has been successfully re-installed, the Percussion DTS Windows Service will start
Uninstalling the Patch
This patch includes an uninstall option to support rollback in the event the patch introduces a problem or issue. The patch can be downloaded from the Support portal. For instructions on installing or uninstalling the patch, please review the Readme file provided in the patch folder. Note: To install a patch after uninstalling an existing patch, uninstall the existing patch, start the service back up normal, shut the service down and then install a patch.