After being deployed on a server, the FanRuan project may encounter crashes due to various reasons.
Restarting a project directly after a crash without capturing a dump file will make root cause identification extremely difficult.
This not only prevents quick resolution of the issue but also makes it impossible to take preventive measures, leading to significant losses of time and effort, which poses considerable challenges for server O&M.
How can you effectively monitor and handle crashes of the FanRuan application to reduce losses in time and effort and smooth server O&M?
FineOps supports invocation the crash handling tool within the O&M project to monitor and automatically handle crashes of the FineRuan application.
1. If a crash is detected in the O&M project, a dump file will be generated, the project will be restarted, and the process will be recovered.
2. By analyzing the generated dump file, you can identify the crash cause quickly, thereby addressing the issue promptly and taking effective preventive measures to enhance the system stability.
This document details how to enable automatic crash handling and configure related crash handling strategies.
The crash handling tool is an independently running component within an O&M project. FineOps relies on this tool for crash monitoring and automatic project restart.
If the main application process is terminated, the crash handling tool will shut down accordingly under specific conditions.
During working hours (6:00 to 23:00): If the main application process is terminated, the crash handling tool will shut down after a five-minute delay.
During non-working hours (0:00 to 6:00 and 23:00 to 24:00): If the main application process is terminated, the crash handling tool will not shut down.
The operation of the crash handling tool requires a free and available port on the server where the application resides.
For FineOps-deployed projects, the port for the crash handling tool is configured and verified for availability during deployment. Therefore, no additional port setting is required.
For projects not deployed via FineOps, you must manually set the port to be used by the crash handling tool and ensure it is available.
1. Log in to FineOps as the admin, click an O&M project, and choose Availability Statistics > Crash Handling Strategy.
2. Enter the port number in Port Setting. The default port is 12100. Enter a port number between 1024 and 65535.
3. Click Test. A prompt will appear: "The port is available. After saving, the crash handling tool will restart with its port updated to the new one."
4 Click Save to apply the changes.
Usage Prerequisite
Strategy Enabling
Enable Auto Restart Upon Crash and click Save to apply the change.
Strategy Implementation
When Auto Restart Upon Crash is enabled and components, including FineReport, FineDataLink, FineBI - Application Node, Engine - Calculation Node, and Engine - Metadata Node, continue to experience high load after consecutive FullGC events (specifically, five consecutive FullGCs with a load score greater than 100), the corresponding component/project will restart automatically.
This setting item is not provided.
For projects deployed via FineOps, this function is provided by containers.
Enable Auto Process Recovery. After enabling Auto Process Recovery, you can set the effective time range of this function.
Click Save to apply the changes.
The process of the FineReport, FineDataLink, FineBI - Application Node, Engine - Calculation Node, or Engine - Metadata Node component that disappears within the effective period will automatically recover.