Changes for page 204 - Found It
Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 81.1
edited by Erik Bakker
on 2023/05/16 09:06
on 2023/05/16 09:06
Change comment:
There is no comment for this version
To version 79.1
edited by Erik Bakker
on 2023/05/12 08:25
on 2023/05/12 08:25
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -18,9 +18,5 @@ 18 18 * Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952) 19 19 * Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947) 20 20 * Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture. 21 -* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again. Note that to make this functionality available a new "base image" was created which will automatically be applied to all gen two karaf containers when you create a new release and deploy it via the deployment plan causing redeployments.21 +* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again. 22 22 * Design - Message Definitions: "Message format" button is also available in view mode. (#919) 23 - 24 -====Remarks==== 25 - 26 -* Manage - Statistics: Improved rollup and storage of metrics when running your solution in the next generation archticture. Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off.