No Data Delivered to Backend System

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 backend system.

2. Problem

The problem in this case was that the backend system was not receiving any data. This was caused by an unstable H2 database.

3. Analysis

3.1 Reproduction

N/A

3.2 Analysis

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.

4. Result

The removal and re-addition of the H2 database caused the H2 database to return to normal behavior. Afterwards, the problem did not reoccur.

5. Suggested Additional Readings

N/A