close

Filter

loading table of contents...

Release Notes / Version 12.2412.0

Table Of Contents

Using java.time.Duration in ConfigurationProperties for human-readable Duration Specification

To be able to use human-readable duration configurations such as 1d in favor of 86_400 given as seconds, a bunch of properties got transformed to hold java.time.Duration instead of long or int values denoting milliseconds, for example.

The following is a list of affected properties that benefit from this change:

  • caas

    • commerce.assetsearchservice.cache-seonds

    • search.cache

      • seconds

      • querylist-search-cache-for-seconds

    • strict-transport-security-header.max-age

  • cae.sitemap.period-minutes

  • cap.server

    • blob-channel-timeout

    • cache

      • group-cache-status-interval

      • resource-cache-status-interval

      • rights-cache-status-interval

      • user-chache-status-interval

    • kicense-reload-interval-millis

    • session-ping-interval

    • termination-timeout-seconds

    • unique-db-access-write-interval

  • elastic.core.event-collection-ttl-sec

  • publisher

    • connection-timeout-seconds

    • status-interval

  • replicator.check-timeout

  • repository.connect-retry-delay-seconds

  • solr

    • connection-timeout

    • socket-timeout

    • zookeeper.client-timeout

    • zookeeper.connect-timeout

  • sql

    • pool

      • check-timeout

      • open-timeout

      • reaper-interval

      • reaper-timeout

      • validator-interval

      • validator-timeout

    • store

      • collector

        • blob-preservation-period

        • delay

        • initial-delay

        • start-time

      • sgml-cache-interval-seconds

  • workflow.server

    • session

      • reaper-timeout

      • timeout

    • termination-timeout-seconds

    • tx.idletimeout

    • uapi.session-pool.max-idle-time-ms

The following unused properties were removed:

  • commerce.hub.data.endpoint.shutdown-timeout-millis

  • workflow.server.sweep.delay

  • workflow.uapi.connect-retry-delay-seconds (use repository.connect-retry-delay-seconds instead)

Upgrade Information

In general, no additional upgrade steps should be required. Nevertheless, you may experience incoming changes, especially to our default application.properties we ship with CoreMedia Blueprint, where we changed respective properties to the human-readable form.

Properties using the old unitless format are still supported and use the same default unit as they did before.

(CMS-24149)

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

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