Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 484.1
edited by Carlijn Kokkeler
on 2024/04/23 15:03
Change comment: There is no comment for this version
To version 486.1
edited by Carlijn Kokkeler
on 2024/04/23 15:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,7 +18,13 @@
18 18  
19 19  [[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
20 20  
21 -{{info}}{{/info}}
21 +{{info}}With the release of Spring 6 in our previous release, some users reported that their filters have begun logging warnings about discarding messages even though the filter is configured to not throw an exception on rejection. For flows that process high numbers of messages (and potentially discard a lot of messages as well) this can significantly disturb the overview of the logs in the manage phase.
22 +
23 +To mitigate this, you can change the filter that throws the warning so it specifically refers to a discard channel. Given the chosen configuration, we advice to use the nullChannel option. This will silently drop the message without registering a warning in the log. In case you find the warning in the log a nice addition, we suggest to add an explicit discard channel leading to a logging outbound channel adapter. This log component can then be configured to throw a warning.
24 +
25 +In the next release, we will aid you by adding a validation check that will force you to select a discard channel when it is currently not selected once you edit the flow to create a new version. More on this in the next release blog. {{/info}}
26 +
27 +
22 22  == **Bug Fixes** ==
23 23  //__Error handling__//
24 24  When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.