PASSEDqueue / zombie_processes

ActiveMQ 6.1 Spawning Zombie Processes on Windows 10 Enterprise

ActiveMQ 6.1 is not reaping child processes, leading to thousands of zombie (defunct) processes. Process table filling up, new process creation at risk.

Pattern

PROCESS_CRASH_LOOP

Severity

HIGH

Confidence

72%

Remediation

Auto-Heal

Test Results

Metric	Expected	Actual
Pattern Recognition	PROCESS_CRASH_LOOP	PROCESS_CRASH_LOOP
Severity Assessment	MEDIUM	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 17298. 2919 zombie child processes. Process table usage at 85%. New fork() calls starting to fail.

Injected Error Messages (1)

ActiveMQ 6.1 crash loop spawning zombies on Windows 10 Enterprise — 2919 defunct child processes under PID 17298, process table 85% full, activemq service restart fail, fork failures imminent

Neural Engine Root Cause Analysis

Process crash loop detected — a service is repeatedly crashing and restarting, failing to reach a stable running state. This indicates a persistent issue such as a missing dependency, corrupted configuration, incompatible library version, memory corruption, or an unhandled exception that occurs during startup. In Kubernetes environments, this manifests as CrashLoopBackOff with exponentially increasing restart delays.

Remediation Plan

1. Check service logs immediately before each crash for the error message or stack trace. 2. Look for core dumps in /var/crash/ or the configured core dump location. 3. Verify all dependencies (config files, environment variables, database connectivity) are available. 4. Roll back to the last known working version if the crash started after a deployment. 5. For segfaults, check for library version mismatches or corrupted binaries — reinstall the package.

Improvements Applied

Severity: HIGH (expected MEDIUM)

Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnqcl40659lig7jzxphmdw