Skip to Content
Version 3.1 by Eva Torken on 2024/03/22 15:42
Show last authors
1 {{container}}{{container layoutStyle="columns"}}(((
2 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.
3
4 Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5
6 == 1. Situation ==
7
8 No data is delivered to a backend system.
9
10 == 2. Problem ==
11
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
14 == 3. Analysis ==
15
16 === 3.1 Reproduction ===
17
18 N/A
19
20 === 3.2 Analysis ===
21
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
24 == 4. Result ==
25
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
28 == 5. Suggested Additional Readings ==
29 N/A
30
31
32 )))((({{toc/}}))){{/container}}{{/container}}