Skip to Content

Changes for page R13 - Double Lane

Last modified by Erik Bakker on 2022/06/16 13:13
From version 8.1
edited by Erik Bakker
on 2022/06/16 12:47
Change comment: There is no comment for this version
To version 14.2
edited by Erik Bakker
on 2022/06/16 13:11
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -61
1 +R13 - Double Lane
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.Release Information.Build numbers.WebHome
1 +Main.Release Information.Cloud Templates.WebHome
Content
... ... @@ -1,20 +1,17 @@
1 -Small update that fixes three specific issues.
1 +Small update that improves platform error handling.
2 2  
3 3  Find out more in our [release blog]
4 4  
5 5  
6 -===== Minor Changes =====
6 +===== Major Changes =====
7 7  
8 -* Updated bundle 'com.emagiz.bundles.groovy-all' from 3.0.9.1 to 3.0.9.2
9 -* Removed bundle 'com.sun.mail.javax.mail' because it was not used anymore
10 -* Updated bundle 'com.emagiz.components.security' from 7.1.1 to 7.2.0
11 -* Updated bundle 'com.emagiz.components.http' from 7.2.1 to 7.2.2
12 -* Updated bundle 'com.emagiz.util.codec' from 6.1.0 to 6.1.1
8 +* Multiple improvements to the 'Error to XML transformer' to prevent error messages from growing too large in certain circumstances, which could negatively impact performance and stability:
9 + ** Removed the 'omit stack trace' functionality: this option wasn't used in eMagiz (defaulted to 'true') and would significantly increase the size of errors by including full stack frame info (Java class names, method names, line numbers, etc).
10 + ** Message history is now truncated to 100 entries max (keeping the first and last 50). Normally message history would never reach this limit, but when building (potentially infinite) loops in eMagiz flows it was possible to create humongous 'history' headers.
11 + ** Message headers are now truncated to 40 entries max (keeping the first 40 headers alphabetically).
12 + ** XML validation errors are now truncated to 40 entries max (keeping the first 40 validation errors reported by the underlying validation engine).
13 + ** "Caused by" exception chains are now truncated to a maximum depth of 5 levels. In normal circumstances exceptions would not be expected to reach this limit, but flows with incorrectly configured custom (recursive) error handling could cause extremely long exception chains.
13 13  
14 -===== Bug Fixes =====
15 +===== Minor Changes =====
15 15  
16 -* The OAuth 2.0 authorization interceptor in the Rest Template component contained client 'Authentication methods’ that were invalid and caused a flow not to start in build 59. Also the clockskew is now configurable so we can handle the requirements of more oauth2 authentication providers.
17 -* The Amazon S3 authentication interceptor in the Rest Template component had a threading issue where the key would be invalid on heavy usage. The threading has been changed and is now behaving correctly.
18 -* In several flow designer components you can add Groovy scripts. Since build 59 using FastStringUtils (JSON parsing) did not work.
19 -* For Gen3 runtimes we upgraded to Spring Boot 2.6.6 to bring the latest security patches.
20 -
17 +* Updated bundle 'com.emagiz.components.error' from 7.0.0 to 7.1.0