Cloudstack 4.20 UI becomes irresponsive. Restart the server to recover, it happens every 10 days.

Description:
I'm experiencing a critical issue with CloudStack 4.20 where all API endpoints become unresponsive approximately every 10 days. The only temporary resolution is to restart the CloudStack management server.

Observed Behavior:

API requests timeout/fail completely after ~10 days of uptime

No explicit ERROR messages in logs prior to outage

Found an unusually large INFO-level log entry (3MB per line) that might be relevant

Attached log file: [filename.log] (Please ensure you actually attach the file via GitHub interface)

Environment:

CloudStack Version: 4.20.0.0

OS:Ubuntu 24.04

Steps to Reproduce:

Start CloudStack management server

Operate normally for ~10 days

API services become unavailable without obvious triggers

Expected Behavior:
API endpoints should remain available continuously without requiring manual restarts.

Additional Context:

The large INFO-level log entry repeats periodically (full content attached)

No observed resource exhaustion (CPU/MEM) before outages

Problem persists across multiple maintenance windows

Troubleshooting Attempted:

Reviewed standard error logs - no smoking gun

Monitored system resources - no apparent bottlenecks

Server restart temporarily resolves the issue

Request:
Please help investigate:

Potential memory leaks or thread blocking in the 4.20 codebase

Significance of the oversized INFO log entries

Update to Original Issue:
Further analysis of the oversized INFO log reveals repetitive entries related to createVPCOffering API calls. The JSON payload in these logs appears to be abnormally large (3MB per line) and contains repetitive configuration data.

Key Log Excerpt Pattern:
INFO [c.c.a.ApiServlet] (qtp123456789-42:) {cmd="createVPCOffering", ... JSON payload (3MB) ...}


Bắt đầu bằng việc xem lại log đính kèm và các mục createVPCOffering lặp lại, tập trung vào mẫu payload INFO 3MB. Sau đó kiểm tra đường dẫn API CloudStack 4.20 được biểu diễn bởi ApiServlet và tái hiện sự cố ngừng hoạt động kéo dài khoảng 10 ngày nếu có thể; được xem là hoàn tất khi đã xác định nguyên nhân, xác định thay đổi mã bị ảnh hưởng và xác nhận rằng các yêu cầu API vẫn khả dụng mà không cần khởi động lại.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.