DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
48 lines
2.1 KiB
Markdown
48 lines
2.1 KiB
Markdown
---
|
|
kind: CONCEPT
|
|
slug: messaging-inbox-jdbc-postgresql-c05
|
|
title: 일시적 인프라 문제가 재시도 불가로 분류된다
|
|
topic: state-machines-and-ownership
|
|
project: clean-architecture-backend-template
|
|
status: 게시 전
|
|
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
rootTreeNode: concept:messaging-inbox-jdbc-postgresql-c05
|
|
evidenceCapturedOn: 2026-09-01
|
|
assets:
|
|
- key: messaging-inbox-jdbc-postgresql-c05
|
|
file: ../../../final/evidence/rendered/messaging-inbox-jdbc-postgresql-c05.svg
|
|
evidence:
|
|
- ../../../final/evidence/raw/messaging-inbox-jdbc-postgresql-c05.txt
|
|
source:
|
|
- 원본 분석 절은 analysis/messaging/messaging-inbox-jdbc-postgresql.md#L329 이다.
|
|
module: messaging-inbox-jdbc-postgresql
|
|
---
|
|
|
|
# 일시적 인프라 문제가 재시도 불가로 분류된다
|
|
|
|
SQL 실패 셋이 전부 `MessagingConfigurationException`이고 그 카테고리는 `CONFIGURATION`, `retryable = false`다. 그런데 `SQLException`의 원인은 대부분 일시적 인프라 문제다.
|
|
|
|
## 관계
|
|
|
|
- **컬럼 폭은 애플리케이션 검증과 짝을 이룬다**
|
|
같은 분석 리프에서 끌어낸 규칙이다.
|
|
- **같은 안전 규칙은 한 공식과 한 강제 시점을 갖는다**
|
|
같은 분석 리프에서 끌어낸 규칙이다.
|
|
|
|
## 본문
|
|
|
|
<!-- body:start -->
|
|
|
|
**SQL 실패 셋이 전부 `MessagingConfigurationException`이다.** 그 예외의 카테고리는 `CONFIGURATION`이고 `retryable = false`다. 그런데 `SQLException`의 원인은 대부분 **일시적 인프라 문제**(연결 끊김, 데드락, 타임아웃)다. 즉 재시도 가능한 실패가 재시도 불가로 분류된다. §17.
|
|
|
|
## MessagingConfigurationException 참조 위치
|
|
|
|
:::evidence key="messaging-inbox-jdbc-postgresql-c05" alt="코드베이스에서 MessagingConfigurationException 를 검색한 출력 19줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="MessagingConfigurationException 코드베이스 검색 — 19줄 · exit 0" zoom="true"
|
|
:::
|
|
|
|
## 분류가 정확한 하나
|
|
|
|
`INBOX_ACTION_FAILED`만 `TRANSIENT_INFRASTRUCTURE`/`retryable = true`이고 예외가 아니라 `HandleResult`로 흐른다.
|
|
|
|
<!-- body:end -->
|