Skip to content

SSE: report socket timeouts through onFailure and reconnect - #926

Open
arturobernalg wants to merge 1 commit into
apache:masterfrom
arturobernalg:sse-timeout-failure
Open

arturobernalg wants to merge 1 commit into
apache:masterfrom
arturobernalg:sse-timeout-failure

Conversation

@arturobernalg

Copy link
Copy Markdown
Member

SocketTimeoutException extends InterruptedIOException and DefaultEventSource#isBenignCancel classified it as a benign cancellation. A read timeout closed the stream with onClosed(), without onFailure() and without a reconnect.

With a client configured with a socket timeout, a server that sends one event and goes silent leaves the application with no failure callback and no further connection attempts. A socket timeout is a network failure, so it now reaches onFailure(ex, willReconnect) and follows the backoff policy. A plain InterruptedIOException is still treated as benign.

Reproduced against a local server that sends one event and stays silent, client with a 5 second soTimeout: before, onClosed at 5.0s, no onFailure, 1 connection; after, onFailure(SocketTimeoutException, willReconnect=true) every ~5s and a new connection each time (4 in 20s).

Tests: new DefaultEventSourceIntegrationTest cases fail on master and pass with the change; httpclient5-sse verify with checkstyle, 53 tests, 0 failures.

…f closing silently

SocketTimeoutException extends InterruptedIOException and was classified
as a benign cancellation by DefaultEventSource#isBenignCancel. A read
timeout closed the stream with onClosed(), without onFailure() and
without a reconnect.
@ok2c

ok2c commented Nov 3, 2026

Copy link
Copy Markdown
Member

CC @shinseongsu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants