Back to All Scenarios
PASSEDqueue / hung_process
ActiveMQ 6.1 Process Hung — Not Responding to Health Checks on Windows 10 Enterprise
ActiveMQ 6.1 process is alive but completely unresponsive. Health checks timing out. Thread/connection pool exhausted. Requires restart.
Pattern
TIMEOUT
Severity
HIGH
Confidence
60%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | TIMEOUT | TIMEOUT | |
| Severity Assessment | HIGH | HIGH | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
Windows 10 Enterprise. ActiveMQ 6.1 PID 39320 running but not responding. All worker threads blocked. Health endpoint timing out. Last successful response 37 minutes ago.
Injected Error Messages (1)
ActiveMQ 6.1 hung on Windows 10 Enterprise — process alive (PID 39320) but timeout on all requests, ETIMEDOUT after 30s, all worker threads blocked, last response 37 minutes ago
Neural Engine Root Cause Analysis
Request timed out — service may be under heavy load, experiencing network issues, or behind a slow upstream.
Remediation Plan
Check server resource utilization (CPU/memory/disk). Investigate network path. Consider scaling if load-related.
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnq49a0581lig7k8egsgqf