Skip to Content

Changes for page 55

Last modified by Erik Bakker on 2023/01/23 13:58
From version 12.1
edited by Erik Bakker
on 2022/06/16 12:59
Change comment: There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2022/06/16 13:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -57
1 +56
Content
... ... @@ -1,21 +1,17 @@
1 -Small update that brings support for connecting to OAuth 2.0 resources servers that do not support having OAuth 2.0 scopes. Also the HTTP component is updated with new REST template possibilities.
1 +Small update that improves platform error handling.
2 2  
3 3  Find out more in our [release blog]
4 4  
5 5  
6 -===== New Features =====
6 +===== Major Changes =====
7 7  
8 -* With this update, eMagiz runtimes can fulfil the role of an MQTT broker. To do this, put an Artemis server support object in your connector and make sure it accepts MQTT protocol communication over web sockets. Internally, handling these (MQTT) messages is no different from handling "normal" (AMQP) messages.
9 -* Updated Artemis, Qpid, Proton-J and Netty to the latest maintenance releases. These updates mostly contain bugfixes, improvements and performance wins.
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.
10 10  
11 11  ===== Minor Changes =====
12 12  
13 -* Updated bundle 'com.emagiz.bundles.spring-security-config' from 5.3.4.1 to 5.3.9.1
14 -* Updated bundle 'com.emagiz.bundles.spring-security-core' from 5.3.4.1 to 5.3.9.1
15 -* Updated bundle 'com.emagiz.bundles.spring-security-oauth2-client' from 5.3.4.1 to 5.3.9.1
16 -* Updated bundle 'com.emagiz.bundles.spring-security-oauth2-core' from 5.3.4.1 to 5.3.9.1
17 -* Updated bundle 'com.emagiz.bundles.spring-security-oauth2-jose' from 5.3.4.1 to 5.3.9.1
18 -* Updated bundle 'com.emagiz.bundles.spring-security-oauth2-resource-server' from 5.3.4.1 to 5.3.9.1
19 -* Updated bundle 'com.emagiz.bundles.spring-security-web' from 5.3.4.1 to 5.3.9.1
20 -* Updated bundle 'com.emagiz.components.security' from 7.0.0 to 7.0.1
21 -* Updated bundle 'com.emagiz.components.http' from 7.1.0 to 7.1.1
17 +* Updated bundle 'com.emagiz.components.error' from 7.0.0 to 7.1.0