Skip to Content

Changes for page V3.1.3

Last modified by Erik Bakker on 2024/09/10 10:38
From version 7.1
edited by Carlijn Kokkeler
on 2024/01/18 09:30
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 -V2.1.0 - Reverted
1 +V3.0.4
Content
... ... @@ -1,22 +1,13 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}(((
3 3  
4 -{{warning}}This image has been reverted due to reported issues with the start/stop flow overview whilst deploying this new image.{{/warning}}
5 -
6 6  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"]].
7 7  
8 -=====New features=====
6 +=====Bug fixes=====
9 9  
10 -New components to support a failover setup:
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 11  
12 -* Clustered lock registry: obtain a lock that can be shared over different containers
13 -* Leader initiator: Used to automatically start and stop roles based on whether they can obtain a cluster-wide lock
14 -* New & extended operations for controlling integration components
15 -** New: Start & stop all components in a specific role, so you can start and stop multiple components at the same time
16 -** New: List all roles and whether they support leadership
17 -** Extended: List flow components now also shows whether a component is configured to be in a role
18 -
19 -Deploy - Deployment plan: to incorporate failover actions during deployment, two new deployment step types are introduced namely “Group” and “Failover”.
20 -
21 21  )))((({{toc/}}))){{/container}}
22 22  {{/container}}