Fixed Loading of Multiple Document Type Model Files in XML Repository

Loading of multiple Document Type Model (DTM) files for the XML Repository was broken and has been fixed now. Multiple DTM files may again be stated as a comma-separated list with property repository.params.contentxml of test class annotation @TestPropertySource (see Blueprint workspace for examples).

(CMS-24773)

Fixed Content ID Comparison on Client-Side Query

QueryService#getContentsFulfilling(...) did not work for numerical Content ID comparisons, e.g., TYPE Document_ : id > 10000, and threw an exception. This is fixed now.

(CMS-24765)

Improved Performance for Large Structs

The code for loading struct properties was optimized, especially for large structs. This speeds up various operations for content that contains a larger struct value.

(CMS-24310)

Improved Publication Performance

The code for destroying intermediate versions after publication was optimized, especially for very large version histories, and/or if many derived multi-site contents exist with possibly large version histories. This reduces the time needed for publication for some cases.

(CMS-24109)

Content Server DB Transaction Retry

The Content 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 Content Server for retries, use these properties:

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

The number of retries on a single database transaction and the delay are configurable. Set the maximum retries and delay values (see above) large enough to cover prolonged database unavailability during failover.

(CMS-24076)

Configuration of Custom MIME Types

A central configuration for custom MIME Type definitions was added to the Blueprint workspace with file shared/common/modules/shared/custom-mime-types/src/main/resources/org/apache/tika/mime/custom-mimetypes.xml. All relevant CMS components depend on this configuration file so that MIME Type definitions added here are active everywhere.

(CMS-22943)