close

Filter

loading table of contents...

Release Notes / Version 11.2310

Table Of Contents

CoreMedia Core

motd and tools-context Function Missing in management-tools Container

Due to the switch from openJDK to Amazon Corretto as a base image, there is also a switch from Debian to a CentOS base image and therefore the locations of these convenience scripts changed. This change fixes the behaviour when running with the Amazon Corretto base image.

(CMS-21360)

Fixed Bug that Required Exact User Names for Login

Fixed the bug that users from a specially customized user provider could not log in with a different identifier than the user name. For releases before 2007.1, custom user providers could return users for other login identifiers, but more recent releases prevented this. The possibility has been restored now, so that these custom user providers continue to work.

(CMS-21105)

Fixed NullPointerException in FeedableImpl

When the type of a collection set as feedable element cannot be determined, the type now correctly defaults to String.

(CMS-21065)

The License Check Now Considers IPs of all Network Interfaces

For IP based licenses all network interfaces are considered now and the check passes if there is at least one IP that can be successfully validated against the IP range configured in the license.

(CMS-20799)

Limit Content Server Threads Checking Database Connections

Fixed the bug that the number of threads used by the Content Server for checking database connections wasn't limited. This could have led to instabilities in cases, where many calls to the database are blocked due to some problems with the database. By default, the number of such threads is now limited to twice the maximum number of database connections. The limit can be changed with configuration property sql.pool.check-connection-max-threads as described in the Deployment Manual in section "CoreMedia Properties Overview | Content Server Properties | Properties for the Connection to the Database".

(CMS-20535)

Fixed Parsing of Workflow Timer Element

Timer elements in workflow definitions with relative values but without explicitly setting the property relative are now recognized correctly as 'relative' even for values > 999.

(CMS-20175)

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.