Third-Party Update: Apache James Mime4J

Apache James Mime4J has been updated to version 0.8.10.

(CMS-24288)

Fixed a Bug Where A Publication Workflow With Content Errors Could Be Started

We fixed a timing issue where the start-workflow window would not show content errors and consequently, a publication workflow could be started.

(CMS-24229)

Postgresql driver has been updated

The postgresql driver org.postgresql:postgresql has been updated to 42.6.1.

(CMS-24216)

Third-Party Update: Apache Commons Compress

Third-party library Apache Commons Compress has been updated to 1.26.0 to fix known security vulnerabilities.

(CMS-24210)

Improved Performance Of Deriving Sites

Performance of Deriving Sites via Studio or API (com.coremedia.cap.multisite.SitesService#deriveSite(...)) has been improved.

(CMS-24075)

Improved Logging for Workflow Errors

The Workflow Server logs more details for errors from certain workflow actions. Previously, some important details were only visible with enabled DEBUG logging.

(CMS-24058)

Method Content#copyTo(...) fixed

Method Content#copyTo(...) showed an error with documents whose blob properties had data. This has now been fixed.

(CMS-24051)

Fixed CAE Feeder Partial Re-Indexing by Actuator or JMX

Fixed a bug in the CAE Feeder that not all content items were re-indexed after a request for partial re-indexing via Spring Boot actuator or JMX.

(CMS-23587)

Extended Workflow Server DB Transaction Retry

The Workflow Server can now be configured to perform retries on database transactions in case of connection loss or read-only databases (MySQL only). These situations may arise in the context of database failovers in setups like, e.g., Amazon Aurora.

To configure the Workflow Server for retries on connection loss, use these properties:

To configure the Workflow Server for retries on a read-only database, use these properties. This is currently only supported on MySQL:

Make sure to set DNS caching on your system to a very short time (probably shorter than workflow.server.tx.retry-on-read-only-db-delay) to allow for refreshed hostname resolution before the next attempt on a previously read-only database is started. This can be necessary to successfully contact the current primary database instance in a database failover setup.

Retries on a single database transaction are limited to 15 times - regardless of which concrete issue arises on each retry. Set the delay values (see above) large enough to cover prolonged database unavailability during failover.

(CMS-23428)

Fixed Feeder Shutdown on Error

Fixed a bug in CAE Feeder and Content Feeder that they did not correctly stop in case of errors that happened during its start. Some threads were not correctly stopped and kept the Java process alive. This has been fixed now.

(CMS-21028)