Release Notes / Version 12.2412.0
Table Of ContentsUpdated Maven dependencies and plugins
Updated several dependency and plugin versions.
The following plugins and dependencies have been updated:
CoreMedia Client API and Mock Adapter for Commerce Hub → 3.0.13
CoreMedia Adapter for Salesforce Commerce Cloud B2C → 3.0.14
CoreMedia Adapter for HCL Commerce → 3.0.12
Apache HttpComponents Client 5 → 5.4.4
AspectJ → 1.9.24
Commons Collections → 4.5.0
Commons Text → 1.13.1
Error Prone → 2.38.0
Google API Common for Java → 2.48.0
Google API Extensions for Java → 2.65.0
Google Auth Library for Java → 1.35.0
Google HTTP Client Library for Java → 1.47.0
GraphQL Java → 22.4
gRPC-Java → 1.72.0
Gson → 2.13.1
Guava → 33.4.8-jre
Hibernate ORM → 6.6.14.Final
Jackson → 2.19.0
JUnit Jupiter → 5.12.2
Micrometer → 1.14.6
Mockito → 5.17.0
Netty → 4.1.121.Final
Reactor Project BOM → 2024.0.5
Spring Boot → 3.4.5
Spring Data BOM → 2024.1.5
Spring Framework → 6.2.6
Spring for GraphQL → 1.3.5
Tomcat → 10.1.41
(CMS-27655)
Case-insensitive User and Group Search
There is a new content server configuration option
cap.server.case-sensitive-member-search. If set to
false, the user and group search in the Studio's
User Manager app works case-insensitively. Default is
true (case-sensitive, backward compatible).
More generally, the option affects the UAPI methods
com.coremedia.cap.user.UserRepository#findUsers and
com.coremedia.cap.user.UserRepository#findGroups.
If you use these methods in custom code, the current behaviour may be
mandatory. In that case leave the option at its default.
(CMS-27644)
Content Server and Workflow Server DB Transaction Retry on Amazon Aurora "Zero-Downtime Patching"
The Content Server can now be configured to perform retries on database transactions in case of connection loss due to “Zero-Downtime Patching” on Amazon Aurora (MySQL only).
To configure the Content Servers for retries, use these properties:
sql.pool.retry-on-connection-loss: enable retries on database connection loss when set to value true (default: false). This is the same property as already available for retries on other connection loss situations.
sql.pool.retry-delay: wait given time before retrying (Duration; default: 15 seconds).
sql.pool.max-retries: maximum number of retries (default: 15).
To configure the Workflow Server for retries, use these properties:
workflow.server.tx.retry-on-connection-loss: enable retries on database connection loss when set to value true (default: false). This is the same property as already available for retries on other connection loss situations.
workflow.server.tx.retry-on-connection-loss-delay: wait given time before retrying on database connection loss (Duration; default: 15 seconds).
Retries on a single Workflow Server database transaction are limited to 15 times.
Set the delay values and retries (see above) large enough to cover prolonged database unavailability during failover.
Make sure to set DNS caching on your system to a very short time (probably shorter than *.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.
(CMS-27224)
Third-Party Update: Apache Tika 3.1.0 and Transitive Dependencies
Apache Tika has been updated to version 3.1.0. As part of this change, the following transitive dependencies of Apache Tika have been updated.
Updated dependencies:
Apache Commons CSV 1.13.0
Apache Commons IO 2.18.0
Apache Log4J API 2.24.3
Apache Mime4J 0.8.12
Apache PDFBox 3.0.4
Apache POI 5.4.1
Apache Tika 3.1.0
Apache XMLBeans 5.3.0
ASM 9.7.1
If you use these libraries in project code, please check their respective release notes for changes and upgrade information.
(CMS-25920)
