Infrastructure Scenario Tests

We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.

21,502
Total Tests
100.0%
Pass Rate
21,502
Passed
0
Failed

Pulsar 3.2 Out of Memory — Killed by OOM Killer on AlmaLinux 9

PASS

The Linux OOM killer terminated the Pulsar 3.2 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

Pulsar 3.2 Out of Memory — Killed by OOM Killer on SUSE Enterprise 15 SP5

PASS

The Linux OOM killer terminated the Pulsar 3.2 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

Pulsar 3.2 Out of Memory — Killed by OOM Killer on Amazon Linux 2023

PASS

The Linux OOM killer terminated the Pulsar 3.2 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

Pulsar 3.2 Out of Memory — Killed by OOM Killer on RHEL 9

PASS

The Linux OOM killer terminated the Pulsar 3.2 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

Pulsar 3.2 Out of Memory — Killed by OOM Killer on Debian 12 Bookworm

PASS

The Linux OOM killer terminated the Pulsar 3.2 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

Pulsar 3.2 Out of Memory — Killed by OOM Killer on Rocky Linux 9

PASS

The Linux OOM killer terminated the Pulsar 3.2 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

Pulsar 3.2 Out of Memory — Killed by OOM Killer on CentOS 9 Stream

PASS

The Linux OOM killer terminated the Pulsar 3.2 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

Pulsar 3.2 Out of Memory — Killed by OOM Killer on Ubuntu 24.04 LTS

PASS

The Linux OOM killer terminated the Pulsar 3.2 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

Pulsar 3.2 Out of Memory — Killed by OOM Killer on Ubuntu 22.04 LTS

PASS

The Linux OOM killer terminated the Pulsar 3.2 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

ActiveMQ 6.1 Out of Memory — Killed by OOM Killer on Windows 10 Enterprise

PASS

The Linux OOM killer terminated the ActiveMQ 6.1 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

ActiveMQ 6.1 Out of Memory — Killed by OOM Killer on Windows 11 Enterprise

PASS

The Linux OOM killer terminated the ActiveMQ 6.1 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

ActiveMQ 6.1 Out of Memory — Killed by OOM Killer on Windows Server 2019

PASS

The Linux OOM killer terminated the ActiveMQ 6.1 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

ActiveMQ 6.1 Out of Memory — Killed by OOM Killer on Windows Server 2022

PASS

The Linux OOM killer terminated the ActiveMQ 6.1 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

ActiveMQ 6.1 Out of Memory — Killed by OOM Killer on Arch Linux

PASS

The Linux OOM killer terminated the ActiveMQ 6.1 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

ActiveMQ 6.1 Out of Memory — Killed by OOM Killer on Fedora 40 Server

PASS

The Linux OOM killer terminated the ActiveMQ 6.1 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

ActiveMQ 6.1 Out of Memory — Killed by OOM Killer on Oracle Linux 9

PASS

The Linux OOM killer terminated the ActiveMQ 6.1 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

ActiveMQ 6.1 Out of Memory — Killed by OOM Killer on AlmaLinux 9

PASS

The Linux OOM killer terminated the ActiveMQ 6.1 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

ActiveMQ 6.1 Out of Memory — Killed by OOM Killer on SUSE Enterprise 15 SP5

PASS

The Linux OOM killer terminated the ActiveMQ 6.1 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

ActiveMQ 6.1 Out of Memory — Killed by OOM Killer on RHEL 9

PASS

The Linux OOM killer terminated the ActiveMQ 6.1 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal

ActiveMQ 6.1 Out of Memory — Killed by OOM Killer on Debian 12 Bookworm

PASS

The Linux OOM killer terminated the ActiveMQ 6.1 process due to memory pressure. The service was the largest memory consumer on the system.

queuePattern: MEMORY_EXHAUSTIONSeverity: CRITICALConfidence: 72%Auto-Heal
PreviousPage 106 of 116Next

Every scenario is tested against Corax's Neural Engine in a production environment with AI-powered root cause analysis.

Tests run continuously as new infrastructure patterns are added.