Skip to Content
Last modified by Erik Bakker on 2024/09/03 13:40
From version 1.1
edited by Eva Torken
on 2024/03/22 12:00
Change comment: There is no comment for this version
To version 5.1
edited by Eva Torken
on 2024/03/26 16:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -No data delivered to backend system
1 +No Data Delivered to Backend System
Content
... ... @@ -5,11 +5,11 @@
5 5  
6 6  == 1. Situation ==
7 7  
8 -No data is delivered to a Mendix application.
8 +No data is delivered to a backend system.
9 9  
10 10  == 2. Problem ==
11 11  
12 -The problem in this case was expected to be related to the old build numbers of the model.
12 +The problem in this case was that the backend system was not receiving any data. This was caused by an unstable H2 database.
13 13  
14 14  == 3. Analysis ==
15 15  
... ... @@ -19,14 +19,15 @@
19 19  
20 20  === 3.2 Analysis ===
21 21  
22 -The problem led us to investigate the health of the JMS and the eMagiz Mendix connector. The JMS was restarted due to the amount of 'client connection failed' warnings that were received. Due to the problem being a Mendix application which was not receiving data, the eMagiz Mendix connector was also restarted. Afterwards, everything worked fine again.
22 +The problem led us to investigate the queue statistics of the flow responsible for delivering the data. Here, it was seen that data was flowing throught the queue, but in a repetitive pattern. In the runtime statistics a very high CPU was observed. Consequently, the health of the H2 database was investigated. The H2 database was processing the messages repeatedly after the connector had undergone auto-healing. Therefore, it was not processing the new messages.
23 23  
24 24  == 4. Result ==
25 25  
26 -The old build numbers used in the model are expected to have an influence on the performance of the eMagiz Mendix connector. We recommend to upgrade these build numbers or to migrate to the current-generation runtime.
26 +The removal and re-addition of the H2 database caused the H2 database to return to normal behavior. Afterwards, the problem did not reoccur. The resetting of the H2 database should also solve the problem. This can be done by moving to Deploy -> Architecture and pressing 'Reset H2'. Do remember that resetting the H2 database or removing and readding it will result in a loss of all the data on the database.
27 27  
28 28  == 5. Suggested Additional Readings ==
29 -N/A
29 +For more information on resetting a H2 Database, please check out the following microlearning:
30 +* [[Reset runtime>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]]
30 30  
31 31  
32 32  )))((({{toc/}}))){{/container}}{{/container}}