No Data Delivered (eMagiz Mendix Connector)
In this document, we will use the information from the actual root cause analysis to make a generic view that can be used if you run into the same or a similar problem in the future. Finally, the document will describe the situation, the problem, the analysis, and the result.
Should you have any questions, please get in touch with academy@emagiz.com.
1. Situation
No data is delivered to a Mendix application.
2. Problem
The problem in this case was expected to be related to the old build numbers of the model.
3. Analysis
3.1 Reproduction
N/A
3.2 Analysis
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.
4. Result
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.