Skip to Content

Changes for page eMagiz Runtime - 5.0.3

Last modified by Erik Bakker on 2022/06/16 13:33
From version 10.1
edited by Erik Bakker
on 2022/06/16 13:31
Change comment: There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2022/06/16 13:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -eMagiz Runtime - 5.0.4
1 +eMagiz Runtime - 5.0.3
Content
... ... @@ -1,12 +1,12 @@
1 -Fourth maintenance release in the eMagiz 5.0.x line. This release fixes Log4J security vulnerabilities CVE-2021-44228 and CVE-2021-45046.
1 +Third maintenance release in the eMagiz 5.0.x line. This release fixes several startup and shutdown related issues.
2 2  
3 -Find out more in our [release blog]
4 4  
5 -
6 6  ===== Bug Fixes =====
7 7  
8 -* Updated OPS4J Pax Logging version 1.10.1 to version 1.11.11. Internally this uses Apache Log4j 2, which is updated from version 2.8.2 to 2.16.0 in this release. This fixed the following two security vulnerabilities:
9 - ** https://nvd.nist.gov/vuln/detail/CVE-2021-44228 (CVSS score 10.0 - Critical)
10 - ** https://nvd.nist.gov/vuln/detail/CVE-2021-45046 (CVSS score 3.7 - Low)
6 +* The lock file is now stored in the data directory. This enables proper EFS locking in the AWS cloud.
7 +* A datadir revision file is introduced. This can be used to identify differences between (versions of) data directories and the runtimes using it.
8 +* Fixed the issue where, in specific cases, having two versions of the same flow might cause auto-startup to skip starting of the flow altogether. This was especially problematic if the flow in question was the infra flow, making it impossible to control the runtime from the iPaaS portal.
9 +* Fixed clearing of auto-started flows, when the runtime was given the shutdown command immediately after starting. This should solve a rare issue where after a restart the runtime would not start any flows, making it impossible to control the runtime from the iPaaS portal.
10 +* The startup process of the runtime will now stop when the runtime is given the shutdown command. Previously, the startup process would still continue when attempting a shutdown during startup, resulting in unexpected behaviour.
11 11  
12 12