Java retries: three timeouts are not one deadline

01 / QUESTION

Seven local HTTP conditions separate retryability, Retry-After, attempt limits and elapsed-time budgets.

METHOD

Freeze protocol and source before execution, save raw records, then independently recompute metrics and verify hashes.

RESULT

Seven local HTTP conditions match expected attempt counts; a 40ms budget returned after 45ms, not a hard real-time guarantee.

OBSERVATIONS

Seven local HTTP conditions match expected attempt counts; a 40ms budget returned after 45ms, not a hard real-time guarantee.

CONCLUSION

Conclusions are limited to the stated variables and acceptance criteria, retaining failures and unverified scope.

LIMITATIONS

Teaching-scale fixed conditions, not online model quality, production throughput or hardware safety. The complete assistant and VL01 remain unfinished.

REPRODUCE

The article provides a pinned revision, environment, runner and independent audit commands.

1. Engineering cases

   Java retries: three timeouts are not one deadline

   Seven local HTTP conditions separate retryability, Retry-After, attempt limits and elapsed-time budgets.

   2026-10-079 MINPublished
2. PROJECT / 002

   Java LLM Practice

   Reproducible Java conversation, retry and persistence boundaries, alongside attention, cache-cost and quantization-error experiments.

   Building
3. Engineering cases

   Java LLM practice (10): why is the reader still running after cancellation?

   30 local HTTP connections separate conversation invalidation, reader exit and server work, comparing Future interruption with socket closure.

   2026-10-0511 MINPublished