Changes for page R13 - Double Lane

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-60
	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,14 +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		-===== Bug Fixes =====
	6	+===== Major Changes =====
7	7
8		-* Build number 59 broke the debugger, build number 60 fixes this.
9		-* Fixed Kafka components not being able to use key- or truststores from the "resources" tab.
10		-* Deploying flows containing a 'Jetty server' support object in build number 59 only worked on the latest runtime version: build number 60 fixes the backwards compatibility with older runtimes. Note that it is still strongly recommended to update to the latest version of the runtime (5.0.4) if you haven't done so already, because this contains fixes for the Log4j security vulnerability.
	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.
11	11
12	12	===== Minor Changes =====
13	13
14		-* Change of behaviour when incoming HTTP headers are mapped to message headers: Up to build 58 the values of incoming HTTP headers were only mapped to an array when it contained multiple values, otherwise the first (and only) value was automatically extracted and used for the message header. Since build 59 the values are always mapped to an array. While this makes the data type of the header more predictable - it is no longer dependent on the number of values a client was sending - it does mean that your SpEL expressions that were previously expecting single values need to now handle array values. In many cases this can be as simple as extracting the first array value like this: "headers.myHeader[0]".
	17	+* Updated bundle 'com.emagiz.components.error' from 7.0.0 to 7.1.0