Technical Guide Reference Guide Frequently Asked Questions Tutorials
Show menu

5.0.2

Release Notes 5.0.2

Fixes

  • Fixed the value of the TLS Certificate Alias attribute of the AS2 Listener being ignored.

  • Fixed session reuse in FTPS components. This impacts Filezilla and ProFTPD servers that expect the same TLS session to be used for both the control and the data connection.
    NOTE: This only works when using TLSv1.2. If the FTPS server only accepts TLSv1.3 connections, session reuse will not work.

  • Fixed missing message parts when using ALL-XML as message part input.

  • Fixed missing commented lines in wrapper.conf for Windows Agent installer.

  • Fixed problem with passwords containing '!'

  • Fixed LICENSE NOT FOUND en Json exceptions in wrapper.log. Caused by handling unexpected GET requests by http-consumer in backend adapters

  • Added analyze query and timing logging.

  • Fixed analyze front-end query delays for huge amount of EmaMessageSummaries.

  • Fixed wrapper.conf log configuration. Logfile name contains date (wrapper-YYYYMMDD.log) and rolls per day/10mb

  • Fixed OpenEdge components, session no longer dynamic.

  • Fixed missing unescaping values in HeaderEnricher V2

  • Fixed StrictHttpFirewall security which no longer allowed double / , backslash and semicolon in URL. Allowed again for backward compatibility.

  • Fixed problem in Control Mail Reporter where default mail address was not handled correctly.

  • Fixed problem in Control/Monitor when monitoring with more than one user.

New features

  • Error notifications from flows can now be switched off via the Control front-end.

  • ControlMailReporter subject config can contain {userid}. Will be replaced by userId.

New Analyze Metrics in control

We have added new analyze metrics to Control, visible when you choose Manage/Status.

Metric Name Description  

Analyze messages stored

The number of Analyze messages successfully stored.

  

Analyze messages received post queue

The number of Analyze messages received after queueing.

Count after pickup from the queue but before storage. The number should be stored + storage errors

Analyze messages received pre queue

The number of Analyze messages received before queueing.

Count in Wiretap

Analyze message storage errors

The number of Analyze messages that could not be stored.

When a message could not be stored it is NOT removed from the queue

Analyze wiretap errors

The number of Analyze wiretap errors.

  

Analyze message processing time

The average time it takes to process an Analyze message from creation to storage.

  

Analyze message max processing time

The max time it takes to process an Analyze message from creation to storage.

  

Analyze message total processing time

The total time it takes to process all Analyze messages from creation to storage.

  

Analyze message size

The average size of Analyze messages in KBs

  

Analyze message max size

The max size of Analyze messages in KBs.

  

Analyze message total size

The total size of Analyze messages in MBs.

  

Analyze messages undeliverable

The number of undeliverable Analyze messages. (After 5 exponential retries)

When a message cannot be stored (due to db connection errors etc) storing will be retried. The retry policy uses exponential backoff meaning the first initial retry will be after 1 minute, then exponentially after 1 minute with a backoff multiplier of 4 for 4 more times (1 minute, 4 minutes, 16 minutes, 64 minutes)

Analyze business entity creation errors

The number of Business Entities creation errors

  

Analyze messages cleanup run deleted

The number of Analyze messages deleted in the current cleanup run.

  

Analyze messages cleanup run total to delete

The number of Analyze messages to delete in the current cleanup run.

  

Analyze messages cleanup total

The number of Analyze messages deleted.

  

Analyze business entity cleanup run deleted

The number of Analyze business entities deleted in the current cleanup run.

  

Analyze business entity cleanup run total to delete

The number of Analyze business entities to delete in the current cleanup run.

  

Analyze business entity cleanup total

The number of Analyze business entities deleted.