Skip to Content

Changes for page V3.1.3

Last modified by Erik Bakker on 2024/09/10 10:38
From version 36.1
edited by Carlijn Kokkeler
on 2024/07/16 14:42
Change comment: There is no comment for this version
To version 28.1
edited by Carlijn Kokkeler
on 2024/04/23 12:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -V3.1.1
1 +V3.0.4
Content
... ... @@ -3,17 +3,11 @@
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 -=====Minor changes=====
7 -
8 -* Added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter.
9 -* Improved the error message when configuring an Infinispan Cache Manager with 'TCP-ping' transport type, when the list of peer hosts are passed in invalid format.
10 -
11 11  =====Bug fixes=====
12 12  
13 -* The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again.
14 -* The initial committed heap memory of runtimes has been lowered to better match actual usage.
15 -* We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
16 -
17 -
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.
11 +
18 18  )))((({{toc/}}))){{/container}}
19 19  {{/container}}