Jan
12
2026
By dev on
mendelson AS2

What is new

  • If the wait time for an MDN exceeded for sync MDN, the outbound connection is now closed by the client. Additional information regarding this issue have been added to the UI help of the system preferences
  • The mendelson AS2 has been localized to Polish
  • Added the system thoughput per month to the server information in the 'About' dialog of the client
  • Added a new option in the server settings that shows additional information in the processing log while processing AS2 messages
  • Added log output if the basic Authentication HTTP Header has been set
  • Added log output if user defined HTTP Header has been set
  • Added a section to the documentation that describes the MDN return values and states of your partner and lists the possible reasons for a failed transmission
  • REST API: added subject and tls entries to the log endpoint, also access to the payload information of transactions
  • REST API: It is now possible to set user defined HTTP headers in the send order endpoint. It is possible to either delete, add or overwrite existing HTTP headers from the system generation and the user defined HTTP header in the partner setting
  • The notification templates have been localized to PT, IT, FR, PL, ES
  • Added a new filter functionality to the partner management, makes it easier to deal with larger amount of partners in the client
  • Modified the internal client-server protocol
  • Added a cache mechanism to certficate access - this increases both the performance of the certificate manager and also the access to certificates
  • Java API: The object AS2RemoteHTTPData has access to the upload time now

 

Resolved problems

  • In the manual send dialog the partner to select were not sorted
  • There was a synchronization problem in the internal client-server interface, sometimes the TLS handshake came up with protocol violations
  • Very seldom there happened a TAG mismatch error in the internal client-server connection. Reason was the external lib MINA 2.2.4, this release rolls back to MINA 2.2.3 and the client-server connection runs again very stable
  • Fixed deadlock problems in the database (mainly Postgres, HSQL has no problems with it) where file delete operations in the maintenance process have been performed while the database was locked
  • In the log there was displayed an upload time and a transmission throughput. These values were not fully correct
  • Data transmission time and transmission throughput was just displayed for outbound transmission. It is now displayed for inbound transmissions, too
  • Added a new locking level to database layer which is less restrictive than the INSERT/UPDATE lock
  • Increased the assignment performance of message handlers for internal client-server messages
  • Increased the mapping performance from OID to algorithm names and algorithm names to OID
  • The postprocessing event (file move) failed if there was no original filename transmitted
  • There were issues if CA root keys were used to encrypt/sign messages (which is uncommon)
  • Added a function to the update routine that filters multiple entries with the same fingerprint from the certificate manager - it seems to be possible for mendelson AS2 2018 and older to import certificates multiple times into the certificate manager
  • Every transaction in the system has assigned temporary files that contain HTTP header, processing steps, anything like this. These files are cleaned up once the transaction is removed/deleted from the system, either manual (client) or by the maintenance process (Preferences-Maintenance). If this one-time file delete process fails, the old transaction files will stay forever in the sent directory of the partner. The temp file delete routine (that cares for the //temp directory and the //_rawincoming directory to clean them up) does now additional checks if there are sent files from old transactions in the messages/receiver/sent/sender of each sender/receiver combination. These files will then be deleted.
  • Modified the lock level for the database transactions for better performance
  • In a single known installation some information String data is too long for a database field and has been cut by the database engine. The field has been redefined with this build, this will be performed automatically with the internal database update procedure. This is not production relevant, just to prevent the database warning which will be also notified by mail
  • The certificate manager has been reworked internally for better performance
  • The CEM module did no longer work, this has been fixed
  • The MDN content was not displayed in the user interface for outgoing asynchronous MDN (worked for sync MDN), the text view was just empty if it was selected
  • The amount of data updated during the transmission processing has been reduced which should result in better performance
  • There was a problem in encoding outbound filenames that contain the '=' character
  • Added several indicies to the database structure for better performance
  • Notification mails have been sent with the default system encoding. This was a problem for languages like Polish. Now all notification mails are send in UTF-8
  • Removed an identified double parsing of inbound signatures for better performance
  • REST API: Fixed an issue with the REST API HMAC security
  • Fixed an issue where you can see the content of a deployed war file via the browser

 

Updated software packages

  • Dependencies: Updated to BC 1.82 (crypto API)
  • Dependencies: Updated to Lucene 12.9 (Index, log search)
  • Dependencies: Updated to Batik 1.19 (SVG support)
  • Dependencies: Updated to HikariCP 7.02 (DB pool)
  • Dependencies: Updated to jackson 2.20 (JSON)