Corax
AboutGet Started

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
All CategoriesServer (9315)Database (5486)Infrastructure (2435)queue (2320)cache (1740)Network (81)Cloud (78)Security (36)VoIP (7)Cascade (4)
All StatusPassedFailed

ActiveMQ 6.1 Failed Graceful Shutdown — Killed with SIGKILL on AlmaLinux 9

PASS

ActiveMQ 6.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ActiveMQ 6.1 Failed Graceful Shutdown — Killed with SIGKILL on RHEL 9

PASS

ActiveMQ 6.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Pulsar 3.2 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 24.04 LTS

PASS

Pulsar 3.2 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Pulsar 3.2 Failed Graceful Shutdown — Killed with SIGKILL on SUSE Enterprise 15 SP5

PASS

Pulsar 3.2 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed Graceful Shutdown — Killed with SIGKILL on Rocky Linux 9

PASS

RabbitMQ 3.13 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed Graceful Shutdown — Killed with SIGKILL on CentOS 9 Stream

PASS

RabbitMQ 3.13 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed Graceful Shutdown — Killed with SIGKILL on Debian 12 Bookworm

PASS

RabbitMQ 3.13 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 22.04 LTS

PASS

RabbitMQ 3.13 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 24.04 LTS

PASS

RabbitMQ 3.13 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed Graceful Shutdown — Killed with SIGKILL on RHEL 9

PASS

RabbitMQ 3.13 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed Graceful Shutdown — Killed with SIGKILL on Amazon Linux 2023

PASS

RabbitMQ 3.13 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

NATS 2.10 Failed Graceful Shutdown — Killed with SIGKILL on Fedora 40 Server

PASS

NATS 2.10 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

NATS 2.10 Failed Graceful Shutdown — Killed with SIGKILL on Arch Linux

PASS

NATS 2.10 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed Graceful Shutdown — Killed with SIGKILL on SUSE Enterprise 15 SP5

PASS

RabbitMQ 3.13 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

RabbitMQ 3.13 Failed Graceful Shutdown — Killed with SIGKILL on AlmaLinux 9

PASS

RabbitMQ 3.13 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

NATS 2.10 Failed Graceful Shutdown — Killed with SIGKILL on Amazon Linux 2023

PASS

NATS 2.10 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

NATS 2.10 Failed Graceful Shutdown — Killed with SIGKILL on SUSE Enterprise 15 SP5

PASS

NATS 2.10 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

NATS 2.10 Failed Graceful Shutdown — Killed with SIGKILL on AlmaLinux 9

PASS

NATS 2.10 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

NATS 2.10 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 24.04 LTS

PASS

NATS 2.10 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

NATS 2.10 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 22.04 LTS

PASS

NATS 2.10 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

queuePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal
PreviousPage 7 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.