Back to All Scenarios
PASSEDqueue / cgroup_limit
ActiveMQ 6.1 Hitting cgroup CPU Throttle on Windows Server 2022
ActiveMQ 6.1 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.
Pattern
HIGH_CPU
Expected: CONTAINER_EVENT
Severity
HIGH
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | CONTAINER_EVENT | HIGH_CPU | |
| Severity Assessment | HIGH | HIGH | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
Windows Server 2022. ActiveMQ 6.1 container CPU quota: 95m. Actual usage exceeding quota. CFS throttle active. Latency spikes during throttle periods.
Injected Error Messages (1)
ActiveMQ 6.1 container restart risk on Windows Server 2022 — cgroup CPU throttle active, container CPU quota exhausted, oomkilled threat from resource pressure, kubelet reporting NotReady, activemq latency critical
Neural Engine Root Cause Analysis
High CPU utilization detected — the server's processor is at or near capacity, causing degraded application performance, increased response times, and potential service unavailability. Common causes include runaway processes, sudden traffic spikes, inefficient code paths, or crypto-mining malware.
Remediation Plan
1. Identify the top CPU-consuming processes using 'top' or 'htop' on the affected server.
2. Check for runaway or zombie processes and terminate them if safe to do so.
3. Review application logs for tight loops, excessive logging, or unoptimized queries.
4. Scale horizontally or vertically if the load is legitimate.
5. Check for unauthorized processes (crypto miners) if CPU usage is unexplained.
Improvements Applied
- Pattern classified as HIGH_CPU (expected CONTAINER_EVENT)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnwwp606yglijg2r7m589i