Back to All Scenarios
PASSEDdatabase / connection_pool
PostgreSQL Connection Pool Exhausted — Idle Connections
The PostgreSQL connection pool is completely consumed by idle connections from a misbehaving application that opens connections but never closes them.
Pattern
UNKNOWN
Expected: DATABASE_CONNECTIONS
Severity
MEDIUM
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | DATABASE_CONNECTIONS | UNKNOWN | |
| Severity Assessment | HIGH | MEDIUM | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
PostgreSQL 16. max_connections=200. 198/200 active (185 idle). Application not closing connections after use. New connection attempts rejected.
Injected Error Messages (1)
PostgreSQL connection pool exhausted — 198/200 connections active (185 idle, 13 running), new connections refused: 'FATAL: too many connections for role', application connection leak detected
Neural Engine Root Cause Analysis
Unrecognized error pattern — this may be a new type of failure not yet cataloged.
Remediation Plan
Trigger autonomous healing to diagnose and fix. Manual investigation may be needed if healing cannot resolve.
Improvements Applied
- Pattern unrecognized — consider adding keywords for DATABASE_CONNECTIONS
- Severity: MEDIUM (expected HIGH)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnoopv001tlig7t0vaunam