Jan
13
2026
By dev on
mendelson OFTP2

What's New

  • Certificate Manager: new structure, tabs removed
  • New icons with improved contrast for the client's Dark Mode and High Contrast Mode added
  • Better output of data transfer rate in the log; this is now dynamic for Byte/s, kB/s, MB/s
  • Transfer counter added; the display is now available in the info dialog
  • The internal client-server protocol has been modified
  • The client has been translated into Polish
  • The notification templates for emails have been translated into French, Italian, Spanish, Portuguese, and Polish
  • New filter functionality for partner management added, making it easier to handle large numbers of partners in the client
  • REST API: New endpoints for partner configuration added
  • REST API: Access to system configuration issues added
  • REST API: Access to server properties and settings added

 

Resolved Issues

  • Indices were missing in the partner-related database table; this is only relevant with a high number of partners
  • Partner cache added using the Caffeine cache library; this speeds up processing and reduces the load on the database. This is only relevant under high load.
  • REST API: A delete request for transactions did not trigger a REST request event in the event log
  • REST API: Sendorder requests are displayed in the event log as certificate renewal events
  • Data throughput increased by optimizing DataExchangeBuffer processing
  • Additional pre- and post-processing paths added in memory for small data transfers. This is significantly faster than the previously used streaming solution and also reduces file I/O. It includes signature generation, encryption, file hash generation, file hash verification, signature verification, decryption, compression, and decompression. For data > 3MB, the system switches to the previous streaming solution to reduce memory consumption
  • Initialization time of OFTP2 protocol fields reduced, leading to a higher data transfer rate
  • Caches added for values that are not production-relevant but serve only for display, e.g., the number of transactions in the system – it is not necessary to update these for every transaction; a lazy update is possible here
  • User-defined post-processing has now been decoupled from transaction processing. There is a separate processing queue where a dedicated process executes the post-processing later. The advantage is a shorter locking time of the corresponding database tables for transactions, which is particularly useful under high load.
  • System performance increased when using a larger number of certificates
  • Performance of the Certificate Manager increased
  • Responsiveness of the client user interface improved by eliminating occasional interface delays
  • Notification emails were not sent in UTF-8, which was an issue for several languages
  • There was an issue when adding and modifying partners regarding partner post-processing events – these were ignored
  • Database deadlock detection added for most database transactions. Deadlocks can occur under heavy load; they have previously only been observed with external databases (e.g., PostgreSQL). If a deadlock is detected, the transaction is rolled back and retried
  • There was an issue with the index of incoming virtual filenames for partners in partner management. When attempting to delete entries with the same subdirectory setup, an incorrect entry could be deleted
  • There was an issue in the XML interface when listing certificates. Bag attributes of PEM-encoded certificates were not XML-encoded
  • Log messages transferred/pushed to the clients are now bundled and sent in a single client-server message; this reduces message overhead
  • Significantly more database access methods set to "automatically retry on deadlock" – this is required for Postgres databases where deadlocks were reported
  • Additional watchdog added that stops connections after a defined time, even if they were set to TCP keep-alive via external infrastructure (e.g., a load balancer)
  • Additional indices added in the database for fast access to transfers
  • Several database-related bottlenecks removed by reducing transaction lookups
  • File I/O errors in preprocessing were ignored; transactions remained permanently stuck when this occurred
  • Additional value added to the logging mechanism as processing log steps were sometimes out of order
  • Cache for system event templates added, for notification and system events
  • Locking time of table locks reduced by decoupling the entire processing logic from the locking logic
  • In the manual send dialog, the partners to be selected were not sorted
  • The check for incoming virtual filenames is now stricter. Any issue with this leads to an SFNA 01 (Start File Negative Answer [invalid filename]). The reason is that unusual virtual filenames could lead to file access problems in the post-processing of incoming messages.
  • Issue with HMAC 256 in the REST API resolved

 

Updated/New Software Packages

  • Dependencies: Updated to Flatlaf 3.6 (dark mode, hicontrast mode)
  • Dependencies: Added caffeine 3.2.0 (cache lib)
  • Dependencies: Updated to Bouncy Castle 1.8.2 (crypto API)
  • Dependencies: Updated to Batik 1.19 (SVG support)
  • Dependencies: Updated to oauth2-oidc-sdk-11.26 (OAuth2 lib)
  • Dependencies: Updated to commons io 1.19
  • Dependencies: Updated to commons codec 1.18
  • Dependencies: Updated to Jackson 2.20 (JSON)
  • Dependencies: Updated to Lucene 9.12.2
  • Dependencies: Updated to HikariCP 7.02 (DB pool)