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 2.1
edited by Eva Torken
on 2024/03/22 15:33
Change comment: There is no comment for this version

Summary

Details

Page properties
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,11 +19,11 @@
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 health of the H2 database. The database had a very high CPU and had high CPU after the connector underwent auto-healing. After further investigation it seemed that the H2 was reprocessing messages and therefore not taking on new ones.
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.
27 27  
28 28  == 5. Suggested Additional Readings ==
29 29  N/A