From 8648825676703e8622ca1f3fe877f6efa965fcbe Mon Sep 17 00:00:00 2001 From: DongHyeonka Date: Thu, 12 Nov 2026 01:16:57 +0900 Subject: [PATCH] =?UTF-8?q?fix(web):=20=EC=9D=91=EB=8B=B5=20=EC=9C=A0?= =?UTF-8?q?=EC=8B=A4=20=EC=8B=9C=ED=97=98=EC=9D=98=20=EC=A4=80=EB=B9=84=20?= =?UTF-8?q?=EC=9A=94=EC=B2=AD=EC=9D=B4=20=EC=9E=A5=EC=95=A0=EC=9A=A9=20?= =?UTF-8?q?=EC=A7=A7=EC=9D=80=20=EC=9D=BD=EA=B8=B0=20=EC=A0=9C=ED=95=9C?= =?UTF-8?q?=EC=9D=84=20=EC=93=B0=EC=A7=80=20=EC=95=8A=EB=8A=94=EB=8B=A4?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 문제: HttpResponseLossFixture.reset()은 시나리오 전에 부수 효과 카운터를 지우는 DELETE다. 이 요청이 응답을 일부러 버리는 호출용 읽기 제한(750ms)을 그대로 썼다. 부하가 높은 runner에서 평범한 reset 응답이 그보다 늦어 JettyCommitThenConnectionResetIT가 시나리오를 시작하기도 전에 SocketTimeoutException으로 실패했다(main run 24, 2026-11-08, 세 번 중 한 번). 고른 방법: 재시도와 부수 효과 조회처럼 넉넉한 HttpFixtureTimeouts.READ_MILLIS를 쓴다. 짧은 제한은 장애를 건 호출에만 남는다. 위험·한계: 시험이 보는 동작은 바뀌지 않는다. 준비 단계가 기다릴 수 있는 시간만 늘었다. 검증: desktop mainCheck(webJettyCompatTest 포함), runner main 수동 실행. --- .../inbound/web/testkit/fault/HttpResponseLossFixture.java | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/adapter/inbound/web/src/testFixtures/java/dev/caskeleton/adapter/inbound/web/testkit/fault/HttpResponseLossFixture.java b/src/adapter/inbound/web/src/testFixtures/java/dev/caskeleton/adapter/inbound/web/testkit/fault/HttpResponseLossFixture.java index fe9fecbe..c0ba1513 100644 --- a/src/adapter/inbound/web/src/testFixtures/java/dev/caskeleton/adapter/inbound/web/testkit/fault/HttpResponseLossFixture.java +++ b/src/adapter/inbound/web/src/testFixtures/java/dev/caskeleton/adapter/inbound/web/testkit/fault/HttpResponseLossFixture.java @@ -41,6 +41,10 @@ public final class HttpResponseLossFixture implements ResponseLossFixture { private void reset() { try { HttpURLConnection connection = open(FaultFixtureProtocol.SIDE_EFFECTS_PATH, "DELETE"); + // The generous timeout, like the retry and the side-effect count. The armed one (750 ms) is + // for the call whose reply the container drops; on a loaded runner an ordinary reset reply + // took longer than that, and the scenario failed before it began (main run 24, 2026-11-08). + connection.setReadTimeout(HttpFixtureTimeouts.READ_MILLIS); connection.getResponseCode(); connection.disconnect(); } catch (IOException e) {