TOLERANT Post Release 12.1

2025/11/09

Notices and Warnings

  • The docker compose examples now contain out commented ulimits for nofiles to prevent errors in case of Rocky/RHEL Docker installations with default ulimits.
  • The XML-elements for automatic reference data updates has been restructured. Update triggers are now configurable via boolean attributes updateOnStart and updateOnStop in element .
  • Reference database types GEOCODING_PARCEL_CENTROID, GEOCODING_ARRIVAL_POINT, GEOCODING_ROOFTOP are not supported/needed any longer. Instead its sufficient to use the generic type GEOCODING. The engine will then pick the best available source.
  • 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 maxErrors and maxServiceErrorPercentage instead. Refer to the manual for details.
    • Batch: Attribute maxErrors was deprecated and replaced with maxBatchErrors.

New Product Features

Configuration and Administration GUI

  • TPR-15307: Added possibility to configure project attribute warnOnErrors in GUI.

Batch

  • TPR-15106: Termination of running batch and initial load process via the frontend now results in a clean termination of the process.

Service

  • TPR-14727: The info endpoint now displays information of the last reference data update.
  • TPR-9043: Reworked the behavior for maximal number of errors.

General

  • TPR-15230: The bundled JRE was upgraded to the latest Java LTS version (21.0.9+11-LTS).
  • TPR-15175: Reworked the structure of automatic reference data update history.
  • 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-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-14919: Upgraded quartz version to 2.4.0 because of CVE-2023-39017.
  • TPR-14806: Added the capability to automatically download reference data for the V6 engine using the element. Refer to the documentation for details on enabling this feature.
  • TPR-14800: Upgraded version of the internal address validation engine for V6 (Version 6.6.0) with numerous improvements across several countries:
    • Canada
      • Address Verification no longer corrects an invalid post code in a returned address when the original input had a missing space between the postal town and the postal code. The issue is observed in an address with post code T2N 1T2.
    • Honduras
      • Address Verification now returns the correct locality when you set the post profile attributematchingScope to LOCALITY_LEVEL in batch mode.
    • Hong Kong
      • Address Verification doesn’t return „BLOCK A“ when you enter „a BLOCK“ in the post.DeliveryAddressLine field.
    • Ireland
      • When you enter an address that has no post.Number or post.Building information, and you enter Ireland as a post.Country element, Address Verification no longer returns the address with an I process status and multiple suggestions
    • Japan
      • Address Verification no longer returns multiple outputs if the input address has the postal code 3080021.
      • Address Verification no longer rejects an address if you put the character 1 as the only data value in an post.AddressLine element.
    • Kosovo
      • If you enter 34/2 as post.Building and post.SubBuilding values respectively in a concatenated string Address Verification now correctly parses the building and sub-building level details to the output address.
      • Address Verification correctly recognizes Prishtina as a synonym of the locality Pristina.
    • Thailand
      • Address Verification correctly validates address at the locality level. If your address contains three localities, the engine no longer returns the output with an A process status with only two localities.
    • United Arab Emirates
      • In batch mode, Address Verification no longer drops sub-building information from post.AddressLine1 to post.AddressLine2.
    • United Kingdom
      • Address Verification no longer parses a building number as a house number and return an I process status for a valid address. The engine no longer drops post.SubCity information from the address.
      • If you parse an address that is valid but doesn’t contain valid sub-building data, Address Verification no longer returns the address with an I process status, instead of a C process status.
      • For a valid address, Address Verification now correctly returns house number with an A process status.
      • Address Verification now correctly validates an address that contains correct building, sub-building, and street details, but doesn’t contain a house number.
      • For an invalid address, Address Verification no longer returns a blank address type indicator instead of U.
      • If your address contains FLAT A sub-building data, Address Verification no longer parses A as building and FLAT as sub-building. The engine returns the address now with a corrected C process status instead of I.
    • United States
      • Address Verification now return correct floor number for a US address.
      • Address Verification no longer returns an error when you set the post profile attribute rangesToExpand value to All and the maxResultCount value to more than 16 for a US address.
      • Address Verification no longer returns addresses with postal codes in ZIP+1 format instead of ZIP+4 format.
      • Address Verification correctly recognises a dot in an input address, and no longer returns a duplicate address. The engine also now correctly validates an invalid address instead of returning corrected address.
  • TPR-14100: Upgraded version of the internal address validation engine for V5 (Version 5.16.5) with numerous improvements across several countries:
    • Austria
      • Address Verification no longer invalidates a valid address and parses a house number to a level-two street field in the following scenarios:
        • The input address includes street information in a formatted address line.
        • The street name includes a period.
    • Canada
      • Address Verification now parses a house number in an input address correctly if you put a comma after the house number. The engine no longer merges the house number and the street in the output.
      • Address Verification no longer fails recognizes HWY 16E as a street name and returns an I process status for an address that contains HWY 16E in post.AddressLine.
    • Finland
      • If you enter Poste Restante in post.DeliveryAddressLine, Address Verification now correctly recognizes the address as a delivery service address.
    • Gibraltar
      • Address Verification now correctly parses street and building information to an output address when the input address contains Gibraltar as post.Subcity information.
    • Republic of Korea
      • Address Verification now returns correct transliteration outputs with postProfile attribute preferredLanguage set as ENGLISH and preferredScript set to ASCII_SIMPLIFIED.
    • Netherlands
      • Address Verification no longer returns different process status for the same address.
    • Thailand
    • Address Verification no longer parses a house number to a post.Number2 field instead of a post.Number field. The engine now also returns a house number in a post.DeliveryAddressLine.
    • Turkey
      • Address Verification no longer fails to recognize the house number in an input address when the post.DeliveryAddressLine field also contains post.Building and post.SubBuilding information.
    • United Arab Emirates
      • In batch mode, Address Verification no longer drops post.SubBuilding information from post.AddressLine1 to post.AddressLine2.
    • United Kingdom
      • Address Verification no longer behaves inconsistently when an input address contains a building number and no other information in the post.AddressLine1 and repeats the building number with the building information on the post.AddressLine2. The engine no longer adds FLAT as a prefix on the first line, or return inconsistent process status values for the address in batch and interactive modes.
    • United States
      • Address Verification nop longer returns an incorrect county name for addresses in Albermarle county, Virginia.
      • HDS-28771: Address Verification no longer returns an I2 process status for an input address that combines ATTN information and PO BOX information in input data fields post.DeliveryAddressLine or post.AddressLine.
      • HDS-28673: If a valid address contains a two-character directional string with a period after each character, for example N. W., Address Verification no longer returns the address with an I process status.
    • British Virgin Islands
      • Address Verification no longer identifies the United States as the country in the output address when the input address contains Virgin Islands, British as the country name.
  • TPR-13472: Deprecated post profile fields geocodingType. The engine now tries to fetch best possible geocodes values based on configured geocoding database and geocoding related output fields. If no geocoding output fields are mapped then fetching geocodes is disabled by default for performance.
  • TPR-11964: In the runtime configuration for V6 engine it is now possible to set deleteOutdatedRefData attribute which automatically cleans up outdated reference data files if a new version of the file exists in the TLDATA folder.
  • TPR-5719: The reject files have been extended to also include the reason for the rejection of each entry.
  • TPR-432: Reject files are now only written when an entry has been rejected.

Fixed Bugs

General

  • TPR-15201: Attribute country in element now also accepts ISO2 country codes.
  • TPR-15158: Security vulnerability CVE-2025-41249 was removed in the (optional) SOAP service coming with the installation.
  • TPR-14868: Improved implementation of postProfile attribute invalidOnMissingRefData for better handling of specific edge cases.
  • TPR-14740: Adding a new profile or changing the „maxResultCount“ of an existing one of the running service, now requires a service reconfigure, for the changes to take place.
  • TPR-14231: The script postEngineUnlockCodes.sh/.bat now returns XML for engine version 5 and JSON for engine Version 6, when the parameter„–raw“ is passed.
  • TPR-12467: Case-insenstive matching using syonym replacements now supports modes: 20 and 21.

Known Bugs

  • Currently no known bugs.

Archived release notes