Skip to Content

Changes for page V3.0.5

Last modified by Carlijn Kokkeler on 2024/07/17 14:39
From version 28.1
edited by Carlijn Kokkeler
on 2024/04/23 12:12
Change comment: There is no comment for this version
To version 31.1
edited by Carlijn Kokkeler
on 2024/07/17 14:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -V3.0.4
1 +V3.0.5
Content
... ... @@ -3,11 +3,9 @@
3 3  
4 4  These are the release notes for this runtime image. Once a runtime image is released, every new release will utilize this runtime image as base for creating runtime images for docker. For more information on this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]].
5 5  
6 -=====Bug fixes=====
6 +====Bug fixes====
7 7  
8 -* The content-length header is now removed from all messages. With the latest Spring version, this HTTP header was no longer overridden when making HTTP (REST) requests. This could result in an error message ‘Too many bytes written’ or ‘Insufficient bytes written’ if the message contained the content-length header from a previous HTTP call. Behavior of the flow components has been changed so that it will never set the content-length header. **Note**: this means that manually setting the content-length header is no longer allowed. If your flows contain any component explicitly setting or overriding the content-length header, these should be removed.
9 -* SFTP Session Factories with a known-hosts file specified were not parsed properly.
10 -* In flows with a JMS inbound and a Kafka outbound, log messages at error level could occur due to jms_* headers on the message that could not be mapped to Kafka message headers. Since this message would be logged for every message that would be send, this log message has been disabled.
8 +* When using a SOAP outbound gateway with a custom SSL web service message sender, using key- and truststores, the truststores were not correctly used in the network communication, resulting in exceptions with ‘certificate_required’.
11 11  
12 12  )))((({{toc/}}))){{/container}}
13 13  {{/container}}