Files
clean-architecture-backend-…/docs/runbooks/db-idle-in-tx-timeout.md
T

868 B

title, category, error_codes, severity, owner, last_updated, status
title category error_codes severity owner last_updated status
Runbook — DB_IDLE_IN_TX_TIMEOUT (트랜잭션 idle 타임아웃) TRANSIENT_DEPENDENCY
DB_IDLE_IN_TX_TIMEOUT
P2 oncall 2026-06-15 stub

Runbook: DB_IDLE_IN_TX_TIMEOUT (runbook://db/idle-in-tx-timeout)

Symptoms

  • HTTP 503 with error.code=DB_IDLE_IN_TX_TIMEOUT
  • SQLState 25P03; transaction held open too long without activity

Diagnosis

  • Check idle_in_transaction_session_timeout Postgres setting
  • Look for application-level long-running transaction holders

Action

  • Reduce transaction scope in application code
  • Verify spring.jpa.properties.hibernate.connection.timeout is bounded

Escalation

  • Escalate to DBA if connection pool exhaustion results

Stub: Phase D2 — author body after domain adoption. (feature-operational-runbook-contract D9)