• Fixed the uri-encoding in the HTTP and Webservice Gateway being always applied even when the attribute was set to false.
• Fixed the response in the HTTP Gateway not being decompressed when response logging is enabled.
• Fixed message parts not being recorded by Analyze wiretaps even though they are present in the ConnectMessage.
• Disabled Analyze database migration. Please see the section below.

The new Analyze database schema was intended to improve the performance of the cleanup of Analyze messages and business entities. However, the migration process has caused issues for some customers, and we have decided to disable the migration for now.

The Analyze cleanup logic now by default assumes the old schema. This means that the cleanup process will be slower than intended.

A fresh Analyze database, i.e., an Analyze database that does not have an associated schema, will be initialized by the agent with the new schema. One can then use the faster cleanup process that relies on the new schema by enabling the Enable cascading delete Analyze property in Deploy and restarting the agent.

We have previously seen issues with the cleanup process, resulting in large transactions that lock entire tables causing Analyze wiretaps to not be able to write to tables. To mitigate this issue, cleanup happens in batches, e.g. cleaning 10 messages at a time in a transaction.

We have added two new Analyze properties to control this process:

• Analyze cleanup batch size: The number of messages to clean in one transaction. Lowering this number will reduce the time a table is locked, but will increase the time it takes to clean up all messages.
• Analyze cleanup batch pause in milliseconds: The time to wait between the individual cleanup batches. Raising this number allows a user to space out the cleanup process to avoid locking issues but will increase the time it takes to clean up all messages.

The following issue is known to exist and is scheduled to be fixed in the next release:

• FTPS connection issues when connecting to a server that expects the same TLS session to be used for both the control and data connection. These servers include FileZilla and ProFTPD. We are currently testing a fix for this issue, and will contact affected users to test the fix in their environments.