Skip to Content

Changes for page 191 - Fifty Fifty

Last modified by Carlijn Kokkeler on 2024/04/18 13:19
From version 59.1
edited by Erik Bakker
on 2023/01/18 09:06
Change comment: There is no comment for this version
To version 60.1
edited by Erik Bakker
on 2023/01/18 09:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -31,6 +31,20 @@
31 31  
32 32  [[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
33 33  
34 +== **Message Redelivery ** ==
35 +
36 +{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime and the functionality is enabled for you environment.{{/warning}}
37 +
38 +Just as with our current offering we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience we have placed this functionality as well under the "Explore" option in Manage. When selecting the message redelivery option you will see all messages that are currently in need to be redelivered (as an error occurred).
39 +
40 +Just as in the current functionality you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that you can still see the linked error message as you could before.
41 +
42 +On top of that we have added some additional functionality.
43 +
44 +* Search option
45 + ** Original queue name
46 + ** Original message ID (which can be found as a header called jms_messageid in the error message view)
47 +
34 34  == **3rd generation runtime bolstering** ==
35 35  
36 36  This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.