TOLERANT Post Release 12.2

2026/10/20

Notices and Warnings

  • Removed attributes user-1,user-2 and so on in an effort to clean up unused configuration attributes in project.
  • Reworked the behavior for maximal number of errors and subsequent handling of those:
    • Service: maxInternalErrors was deprecated. Added possibility to configure a circuit breaker with the attributes maxServiceErrorWindow and maxServiceErrorPercentage instead. Refer to the manual for details.
    • Batch: Attribute maxErrors was deprecated and replaced with maxBatchErrors.
  • The monolithic structure of the products with service component has been broken down into a more modern, microservice-oriented architecture. The basic shipped TOLERANT application now consists of 7 services:
    • TOLERANT Backend Service: Contains all functionality needed for the technical processing of requests.
    • TOLERANT GUI Service: Contains the Angular GUI.
    • TOLERANT SOAP Service: Supports SOAP calls and routes to the Backend Service (optional).
    • Webserver (NGINX): Gateway for all incoming requests.
    • Identity Provider (Keycloak): Preconfigured identity provider for our example installation (optional).
    • Grafana: Visualization of available metrics (Docker example only).
    • Prometheus: Data collection and querying for later use in Grafana (Docker example only).
  • The default input format delimiter and output format delimiter value has been changed to semicolon.
  • Completely reworked the logging functionalities. Users can now use the full breadth of log4J2 functionalities. To make the switch easier, log4J2 example configurations for different scenarios are shipped with the product. For more information please refer to the manual.
  • Configuration element summaryFile was removed in favor of the new batchSummary.
  • A new version of the H2 database driver (h2-2.3.232) will be used from now on. This also means that customers will have to switch to a new version of our supplementary reference data (e.g. StaB data). This will be shipped together ( in the same folders on SFTP ) with the normal versions of the reference data, which will still be there to support older product versions. The new reference data artifacts will include „_from_12.0“ in the name.
  • Reworked, combined and harmonized the command-line tools for service administration. Now all functionalities for managing the service and much more can be found in the new< service.sh/.exe tool. For a detailed explanation of the new features and usage, please refer to the manual.
  • Removed functionality to „Reconfigure Runtime“ from GUI, backend service and CLI calls. The functionality was too similar to „Reconfigure Service“ and led to confusion.
  • When being in a service instance context in GUI, the GUI and all its configuration settings can now be reloaded from the memory of the running service instance (as opposed to the underlying xml configuration). The menu entries and tooltips were improved to reflect and clarify new (and existing) behavior.
  • Keycloak has been updated to version 26.6.3.
  • Improved address exception handlingAddress exception CSV files can now use separate values for matching and output by adding the output. prefix.

    The enhancement supports:

    • Separate output values for street, house number, locality, postal code, and other Post output fields.
    • Multiple replacements within one exception row.
    • Explicit house-number corrections.
    • Empty explicit values falling back to the existing behavior.
    • More tolerant matching of German umlauts and accented characters.
    • Preservation of spelling and capitalization in explicit output values.
    • Compatibility with existing exception files that do not use output. columns.

    No changes to existing XML configurations are required.

  • 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.
  • JMX beans and JMX bean access was removed due to security considerations and it not being used by customers.
  • 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.
  • Introduced a Helm chart for deploying TOLERANT Post in Kubernetes. The chart is available on TOLERANT GitHub
  • General security updates:
    • Upgraded Java version 21.0.12.1+1
    • Upgraded Nginx to version 1.30.6
    • Upgraded Spring Boot to version 4.1.1

    Fixed the following vulnerabilities:

    • CVE-2026-49844
    • CVE-2026-40983
    • CVE-2026-40984
    • CVE-2026-54291
    • GHSA-q6gh-6v2r-hjv3
    • CVE-2026-54515
    • GHSA-387m-935m-c4vw
    • CVE-2026-71497
    • CVE-2026-59903
    • CVE-2026-65905
    • CVE-2026-65182
    • CVE-2026-68525
    • CVE-2026-84939
    • CVE-2026-68497
    • CVE-2026-91776
    • CVE-2026-91777
    • CVE-2026-89407
    • CVE-2026-89425
    • CVE-2026-75140
    • CVE-2026-8763
    • CVE-2026-13506
    • CVE-2026-107315
    • CVE-2026-107314
    • CVE-2026-107315
  • The example Helm chart now uses the Kubernetes Gateway API instead of Ingress. If you use a custom values.yaml, move the relevant settings from ingress to gateway and review the GatewayClass, listeners, hostnames, TLS, and paths. Install the required Gateway API components and NGINX Gateway Fabric as described in the chart README before deploying.

New Product Features

Configuration and Administration GUI

  • TPR-10704: New search mode GEOCODETOADDRESS and a new field called searchRadius were added to post profile settings.
  • TPR-13005: The static path element inst/1 can now be omitted from the requsts sent to the admin service.
  • TPR-13108: V2 endpoints usage deprecated for GUI
  • TPR-14170: Updated all GUI components to Angular version 19.0.
  • TPR-14266: Reworked and consolidated several icons throughout GUI for better clarity.
  • TPR-15307: Added possibility to configure project attribute warnOnErrors in GUI.

Batch

  • TPR-14120: All batch processes will now report their statistics to a batch summary file located under /logs.
  • TPR-15106: Termination of running batch and initial load process via the frontend now results in a clean termination of the process.

Service

  • TPR-9043: Reworked the behavior for maximal number of errors.
  • TPR-10137: Improved scrolling and reloading of console output when executing background jobs via GUI wizard.
  • TPR-12029: Service registration for Windows has been reimplemented and improved to better support the current multi-service setup. The functionality is included in the new service.exe tool.
  • TPR-12599: A new /info endpoint for all products has been introduced. For example: http://localhost:8080/postService/info. This endpoint can be used to monitor details about the product. For example: Post info endpoint has unlock code and its corresponding expiration date information.
  • 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-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.

API

  • TPR-10622: The following system properties can now be used to configure the java API client:
    • com.tolerantsoftware.api.socketTimeout
    • com.tolerantsoftware.api.connectionTimeout
    • com.tolerantsoftware.api.maxConnections

General

  • TPR-432: Reject files are now only written if at least one record from the input has been rejected.
  • TPR-5719: The reject files have been extended to also include the reason for the rejection of each record.
  • TPR-10958: It is now possible to configure JVM options via specific environment variables (see tolerantEnv.sh/bat for examples).
  • TPR-12499: Reworked the installer to support the new microservice architecture and a simplified option set.
  • TPR-12599: A new /info endpoint for all products has been introduced. For example: http://localhost:8080/postService/info. This endpoint can be used to monitor details about the product. For example: Post info endpoint has unlock code and its corresponding expiration date information.
  • TPR-12614: The docker compose shipment now includes Prometheus and Grafana services.
  • TPR-13005: The static path element inst/1 can now be omitted from the requsts sent to the admin service.
  • 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-13323: Landscape Engine now supports fallbacks for certain postal codes in Japan, which can be set via the following new attributes:
    • fuzzy.PostalCodeFallback: when activated the engine will try to remove ambiguity by validating the postal code only.
    • fuzzy.PostalCodeFallbackReturnCode: can be used to change the default returnCode (0) used when the fallback has taken place.
  • TPR-13857: The profile attribute elementAbbreviation is now supported for version 6.x of the internal addressengine.
  • TPR-14919: Upgraded quartz version to 2.4.0 because of CVE-2023-39017.
  • TPR-15029: Restructured pipeline metrics for standardized naming patterns and better Prometheus compatibility. An overview of all available metrics can be retrieved by calling the /metrics endpoint.
  • TPR-15041: The file permissions in the docker images were revised to minimize the effort needed to start the containers with a local user. For more information please visit our Docker Hub and GitHub repositories.
  • TPR-15175: Reworked the structure of automatic reference data update history.
  • 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-15292: Upgraded version of the internal address validation engine for V6 (Version 6.8.1) with improvements to stability, validation, suggestions, parsing, formatting, and performance across several countries:
    • General
      • Improved stability when processing certain addresses from Thailand and India that could previously cause the engine to stop unexpectedly.
    • Australia
      • Improved the ranking of interactive suggestions when an address contains a house number, street, locality, and postcode.
      • Removed a duplicate locality from interactive suggestions for addresses in Bairnsdale.
    • Canada
      • Improved validation and address suggestions when no postal code is provided.
      • Improved recognition of the post-directional value N.
      • Prevented English street descriptors from being changed incorrectly to French street descriptors.
    • Germany
      • Improved the return of a current address for an archived address when the new-address option is enabled.
      • Prevented the street name Noltenweg from being abbreviated incorrectly when an address cannot be validated in batch mode.
    • Hong Kong
      • Improved suggestions for addresses where incorrect sub-building information could previously be added.
    • Ireland
      • Improved validation of otherwise valid addresses that contain a single-letter province value.
    • Israel
      • Improved the validation of house numbers in multi-line addresses that use mixed Hebrew script.
    • Japan
      • Improved performance when the preformatted-line delimiter is set to None.
      • Resolved parsing errors that could cause very slow processing for certain addresses.
      • Improved consistency between the process status and result quality returned for an address.
      • Improved correction of locality level 3 information.
    • Mexico
      • Improved recognition of Avenida as the same street descriptor as its abbreviated forms.
    • Spain
      • Prevented duplicate sub-building information from being returned.
      • Improved floor information in interactive address suggestions.
    • United Kingdom
      • Improved parsing of organization names supplied in formatted address lines so that they are not returned as contact information.
    • United States
      • Improved validation when matching against outdated addresses is disabled.
      • Improved mixed-case formatting for street names that are not present in the reference data.
      • Improved validation when the street and ZIP Code match but the supplied city and state do not.
      • Improved recognition of a post-directional descriptor at the end of an address and prevented the ZIP Code from being omitted.
      • Prevented valid street names from being changed to uppercase when mixed casing and official alias handling are selected.
      • Improved consistency between address results from versions 5 and 6 of the internal engine.
      • Improved the result quality value returned for valid addresses.
      • Improved recognition of KK as part of a highway name so that highway information is not returned as unrecognized data.
      • Improved recognition of street names and directional identifiers when they are separated by a space.
      • Improved correction of an invalid locality when no ZIP Code is supplied.
      • Ensured that street directional indicators follow the selected mixed or preserved casing.
  • 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-16345: Updated okhttp3 and fixed vulnerabilities CVE-2021-0341 and CVE-2023-3635
  • TPR-17606: Open telemetry tracing is now supported for TOLERANT Post.

Security

  • TPR-12671: It is now possible to configure the software to limit file access to the predefined TOLERANT directories. This setting is activated per default.

Manual

  • TPR-10162: The annex of supported countries has been updated. The data applies to both engines V5 and V6. Single Line Validation is available for all supported countries. For Table A.1, „Part of“ column was added and the legend was adapted.
  • TPR-16066: Released new english manuals.

Fixed Bugs

Configuration and Administration GUI

  • TPR-10122: The wizard for executing background jobs via GUI now scrolls properly to the bottom in case of long console outputs.
  • TPR-10299: The GUI now correctly triggers the notification that requests the user to save the configuration when he navigates to another view.
  • TPR-10423: The checkbox „Use synonyms“ now correctly triggers the synonym processing in file preview in GUI. All environment variables are now replaced when parsing the configuration from JSON.
  • TPR-14404: The GUI now displays an error banner when trying to start an inactive project.
  • TPR-14430: The first element of type InputFieldmap will be used, if the mode attribute is not specified in the service configuration.
  • 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.
  • TPR-17776: Output Switch now correctly shows up in the GUI for a single output as well

Client GUI

  • TPR-10297: Fixed some minor bugs and added small usability improvements in the Client GUI.
  • TPR-10327: Request history in Client GUI is now preserved when switching between Admin GUI and Client GUI.

Service

  • TPR-15002: Proxy configuration were adjusted to handle escape sequences correctly.

General

  • TPR-10180: If a project is in state ERROR it now prevents the cluster synchronization. When the project state has been recovered, the synchronization will resume.
  • TPR-10388: Added additional states in which a project cannot be stopped to increase stability of a running project.
  • TPR-10416: SHUTDOWN DEFRAG for H2 databases is now executed after creating a full savepoint. NOTE: Due to a known issue in H2 implementation itself, theSHUTDOWN DEFRAG command does not work properly with encrypted databases (for H2 native encryption, it will still work with the new application side encryption).
  • TPR-10475: Database consistency check will not remove the schema name from the tablename if included to execute the check.
  • TPR-12467: Case-insenstive matching using syonym replacements now supports modes: 20 and 21.
  • TPR-12978: Misleading errors caused by the V6 engine not returning results were removed from the logfile.
  • TPR-16553: JDBC URLs containing usernames or passwords are no longer logged at INFO level while connecting to a database.
  • TPR-17807: Fixed a race condition while initializing TOLERANT Post internal fields.

Security

  • TPR-10684: Updated postgres driver to version 42.7.7 to address security finding CVE-2022-21724.

Known Bugs

  • Currently no known bugs.

Archived release notes