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>
65 lines
4.1 KiB
Plaintext
65 lines
4.1 KiB
Plaintext
# 주제: 브로커 선택 거절 메시지가 없다고 말하는 것이 실제로는 있고, 실제로 없는 것은 다른 것이다
|
|
# revision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
# severity: P2 (문서/진단 정확성)
|
|
|
|
# ---- 거절 메시지 ----
|
|
# messaging-spring-boot-starter/.../MessagingProviderSelection.java:63-68
|
|
# static final Map<String, String> BROKERS_WITHOUT_A_TRANSPORT =
|
|
# Map.of("rabbit",
|
|
# "the Rabbit adapter ships its validators and security configuration but no "
|
|
# + "MessagingTransport: its native channel publisher is not implemented, so a publish "
|
|
# + "has nothing to travel on");
|
|
# 클래스 javadoc:51-61 도 같은 주장을 한다:
|
|
# "The Rabbit leaf ships its profile validator, failure classifier and security configurer, and
|
|
# no transport — the native channel bridge those would sit on has only test implementations."
|
|
|
|
# ---- 측정 ----
|
|
# command: git grep -n "implements MessagingTransport" -- src
|
|
src/messaging/messaging-kafka/.../KafkaMessagingTransport.java:41
|
|
src/messaging/messaging-nats-experimental/.../NatsJetStreamTransport.java:54
|
|
src/messaging/messaging-pulsar-experimental/.../PulsarMessagingTransport.java:47
|
|
src/messaging/messaging-rabbit/.../RabbitMessagingTransport.java:39 <-- 존재한다
|
|
src/messaging/messaging-runtime-core/src/test/.../DefaultMessagePublisherTest.java:426 (테스트 대역)
|
|
src/messaging/messaging-transport-spi/src/test/.../MessagingRuntimeRegistryTest.java:230 (테스트 대역)
|
|
#
|
|
# RabbitMessagingTransport 는 246줄이며 완성되어 있다:
|
|
# - confirm 과 return 을 RabbitConfirmCoordinator 로 상관시킨다
|
|
# - mandatory 를 항상 세운다
|
|
# - 종료 상태·페이로드 크기를 채널 이전에 검사해 NOT_TRANSMITTED 로 거절한다
|
|
# - 3-arg 생성자는 consumerFactory 가 RABBIT_CONSUMER_NOT_CONFIGURED 를 던진다 (Kafka 와 동형)
|
|
# - CAPABILITIES 를 선언한다 (nativeDeadLetter=true, delayedDelivery=true 등 Kafka 와 다른 조합)
|
|
|
|
# ---- 실제로 없는 것 ----
|
|
# command: git grep -n "RabbitChannelPublisher" -- src
|
|
# RabbitChannelPublisher.java:13 (인터페이스 선언)
|
|
# RabbitMessagingTransport.java:47,61,84 (필드/생성자 파라미터)
|
|
# build.gradle:12 (주석)
|
|
# RabbitBrokerIT.java:93 new RabbitChannelPublisher() {…} <-- 컨테이너 테스트의 익명클래스
|
|
# RabbitRuntimeTest.java:48 new RabbitChannelPublisher() {…} <-- 단위 테스트의 익명클래스
|
|
# => 프로덕션 구현 0. 테스트 익명 구현 2.
|
|
#
|
|
# RabbitChannelPublisher 는 3개 메서드뿐인 작은 인터페이스다:
|
|
# long nextPublishSequence();
|
|
# void publish(long sequence, String exchange, String routingKey, Message message, boolean mandatory);
|
|
# default void close() {}
|
|
# 그리고 왜 두 호출로 나뉘는지가 javadoc 에 있다:
|
|
# "A confirm can arrive on the connection thread before basicPublish has even returned, so a
|
|
# transport that registered its pending publish afterwards would drop that confirm and wait
|
|
# forever for one that already came. Reserving first closes that race."
|
|
|
|
# ---- 판정 ----
|
|
# 메시지의 후반부("its native channel publisher is not implemented")는 정확하다.
|
|
# 전반부("no MessagingTransport")는 부정확하다 — 전송은 있다.
|
|
# 실무적 결과: 이 오류를 읽은 사람이 없는 전송 클래스를 찾아 나서고, 실제 공백인
|
|
# 3-메서드 인터페이스 구현 하나를 놓친다.
|
|
#
|
|
# 그리고 동작하는 구현은 컨테이너 IT 의 익명클래스로 이미 존재한다(RabbitBrokerIT:93).
|
|
# messaging-kafka 의 BrokerTopologyInspector 와 같은 형태다(EVD-319):
|
|
# 프로덕션에 없는 조각이 테스트 안에 이미 쓰여 있다.
|
|
|
|
# ---- 대조: rabbit 은 공유 계약을 통과한다 ----
|
|
# EVD-322: RabbitAdapterContractTest$Contract tests=7 failures=0
|
|
# RabbitBrokerIT tests=4 failures=0 (컨테이너 실행)
|
|
# messaging-testkit 의 CompatibilityMatrix 는 rabbit 을 EXPERIMENTAL / runsSharedContract=true /
|
|
# enabledByDefault=false 로 둔다. 그 표기는 정확하다.
|