Skip to Content

Changes for page R22 - Double lane

Last modified by Erik Bakker on 2025/10/09 10:14
From version 19.1
edited by Erik Bakker
on 2025/10/09 10:14
Change comment: There is no comment for this version
To version 6.1
edited by Erik Bakker
on 2023/04/28 08:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R22 - Double lane
1 +R17 - Double lane
Content
... ... @@ -1,16 +1,15 @@
1 -**Non-service-affecting** final template to use the **R22** double lane release.
1 +Non service affecting final template to use the R17 Double lane release.
2 +Process: To use the new R17 release of our cloud template we upgrade in one steps, the update is non service affecting.
2 2  
3 -**Process**
4 -To use the new R22 release of our cloud template we upgrade in one step. This step is non-service-affecting.
5 -
6 6  **Overview**
7 -* Update versions of dependencies.
5 +This update improves the auto-healing functionality of our current generation runtime architecture. In this cloud template an earlier bug surrounding the "lock reclaim" auto-healing has been fixed.
8 8  
9 -**Update Steps**
10 -* Use the final R22 template (non-service affecting)(duration: < 5 minutes)
7 +**Updates**
8 + * Improve Locking mitigation in the Artemis server (autohealing)
11 11  
10 +**Update Steps**
11 +* Use the final R17 template (non service affecting) (duration: 4 minutes)
12 12  * User actions after applying the final template:
13 -** Check if all runtimes are up via the runtime overview or Deploy Architecture
14 -** Check if all runtimes have been installed according to the active release
15 -** Check if messages pass through the bus by verifying a critical message flow in external systems
16 -
13 +** Check if all runtimes are reachable by the runtime dashboard.
14 +** Check if all flows have been installed according to the active release.
15 +** Check if messages pass through the bus by verifying a critical message flow in external systems.