TOLERANT Match Release 12.1

Notices and Warnings

• All default values for configuration attributes are now automatically loaded from the backend. This reduces maintenance effort and prevents discrepancies between backend and frontend defaults.
• Introduced new frontend elements and layout improvements. This helps to easier guide the user via semantically grouped elements, sliders for setting numerical values and more.
• The XML-Attributes saveSchedule and fullSavepointSchedule are now limited to exact one cron schedule.
• JMX beans and JMX bean access was removed due to security considerations and it not being used by customers.
• The usage of YAML hazelcast configuration is now supported. TOLERANT Match uses the following fallback order to find the hazelcast configuration:
  • hazelcast.yaml
  • hazelcast.yml
  • hazelcast.xml
  • clusterconfig.yaml
  • clusterconfig.yml
  • clusterconfig.xml
• Introduced a Helm chart for deploying TOLERANT Match in Kubernetes. The chart is available on TOLERANT GitHub and includes Kubernetes-oriented configuration examples, best-practice recommendations, and troubleshooting guidance.
• Fundamentally restructured the architecture of GUI component and its orchestration to optimize usage in cloud environments:
  • Moved GUI-related API logic from the frontend service into the backend.
  • Changed the GUI to static resource delivery, removing the separate Java GUI runtime.
  • Split runtime responsibilities into backend, static GUI, and NGINX/proxy routing.
  • Updated installer, Docker, and NGINX templates for the new deployment model.
  • Added compatibility handling for legacy 12.x API endpoints.
  • Updated documentation for removed GUI service, ports, and configuration options.
• The health endpoint now implements two additional selectors:
  • readiness: service is up and ready to accept requests
  • liveness: service is running. This represents a relaxed health check.
• Fully reworked documentation for the Match cluster feature. It is now published on TOLERANT GitHub and consists of several playbooks, best-practice approaches, and troubleshooting tips.
• Updated English service manuals to document version 1.4. All the latest changes are now reflected in both translations, English and German.
• Updated English batch manuals to document version 1.4. All the latest changes are now reflected in both translations, English and German.

New Product Features

Configuration and Administration GUI

• TPR-16607: Added feature to jump directly to the database section for the referenced database when configuring original data.

Service

• TPR-3738: Optimized data sync in Match clusters to minimize the use of full bidirectional syncs. This should reduce the time required for these sync tasks and improve overall IT operations.
• TPR-15470: The XML attributes saveSchedule and fullSavepointSchedule are now limited to exactly one cron schedule.
• TPR-15853: Restricted the selection of search modes in Client GUI. The resultmodes will now be only available if the preconditions are met (e.g. original data is fully configured).
• TPR-15971: Updated Spring Boot version for SOAP to 4.0.6 and fixed vulnerabilities: CVE-2026-29145, CVE-2026-24734, CVE-2026-34483, CVE-2026-34487
• TPR-16353: The attribute cacheSize of the Database element can now be used to limit the memory cache required by RocksDB.

General

• TPR-13176: Introduced the OutputField attribute ignoreEmptyValues, which is set to Y by default. If set to N, positional delimiters are added when more than one OutputFieldMapItem is mapped to a single OutputField.
• TPR-15134: A new synchronization strategy was implemented to facilitate initial load rollout across the cluster. To make initial load data eligible for rollout, the initial load must provide a valid –data-epoch. Please refer to our new cluster documentation under TOLERANT GitHub for more details
• TPR-15208: Upgraded micronaut framework to version 4.10.14 and fixed CVEs: CVE-2026-33012, CVE-2026-33013, CVE-2026-33870, CVE-2026-33871
• TPR-15652: The output of support.sh/bat will now be written to $TLLOGS if $TOLERANT_HOME is not writable.
• TPR-15720: Added support for Informix databases.
• TPR-15826: The usage of ECS Layout is now supported either by using a custom log4j2 profile or by activating the integrated layout by setting the environment variable LOGGING_PROFILE=ecs.
• TPR-15900: Added new env variable TOLERANT_JVM_CUST_PROPERTIES to extend the java properties.
• TPR-16105: Added support for MYSQL and MariaDB databases.
• TPR-16146: Fixed vulnerability GHSA-72hv-8253-57qq.
• TPR-16264: New endpoints are now available to enable the execution of tolerant command line tools on the backend.
• TPR-16454: Extended service.sh/exe to support the nginx reload command.
• TPR-16508: The bundled JRE was upgraded to the latest Java LTS version (21.0.11+11-LTS).

Fixed Bugs

Configuration and Administration GUI

• TPR-15786: Investigated and fixed an issue in the left-hand navigation tree where selected menu items were not consistently highlighted. In certain scenarios, clicking on a child item caused the highlight to shift to its parent or grandparent node, potentially misleading users about the currently active section.

Batch

• TPR-15648: Synonym and normalizer statistics are now shown properly in the batch summary file.
• TPR-16207: The CSV-Writer will no longer escape delimiters in outputs that are surrounded by enclosures.

Service

• TPR-15646: Corrected validation of the TOLERANT Match configuration during incremental initial load.
• TPR-15731: Importing an index with matchServiceTool no longer requires an explicit configuration file. By default, matchserviceconfig.xml under TLCONFIG is used.
• TPR-15739: Serialization of match.InternalData was corrected.
• TPR-16001: The initial loader now accepts match.Key values containing dots.
• TPR-16162: Unidirectional database synchronization now uses checkpoints when synchronizing RocksDB pages. This prevents possible index inconsistencies when using match fields of type PLAIN with large amounts of data and RocksDB.
• TPR-16333: The runtime attribute serviceTimeout is now correctly updated after executing the reconfigure command.
• TPR-16681: Corrected bulk response handling for match.OriginalData and match.InternalData in bulk search and bulk get-by-key operations.

General

• TPR-16235: Empty values for match fields of type Date are now handled correctly.
• TPR-16553: JDBC URLs containing usernames or passwords are no longer logged at INFO level while connecting to a database.
• TPR-16619: Stabilized the ordering of health endpoint details returned by service.sh/exe.

Known Bugs

• Currently no known bugs.