Skip to Content

Changes for page V3.1.2

Last modified by Carlijn Kokkeler on 2024/08/14 10:02
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 29.2
edited by Carlijn Kokkeler
on 2024/05/06 14:19
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -V2.1.0 - Reverted
1 +V306
Content
... ... @@ -1,22 +1,11 @@
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 +* SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call.
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}}