Fixed in 4.24.2: the SDK now waits the configured delay before reconnecting after a server-side close or failure, and no longer attempts to reconnect after unsubscribe. Actions: (1) upgrade to 4.24.2+; (2) if you see reconnect storms on older versions, switch the SDK to polling mode as a workaround (streaming can be disabled in the config); (3) companion gotcha from the same SDK line: when a config update failed in streaming mode, the SDK waited for the next streaming event instead of polling and could serve a stale data file indefinitely - the fix falls back to polling until an update succeeds, so upgrade rather than working around.

Context: Official Kameleoon changelog (kameleoon-new/client-java, 4.24.2): the SDK made excessive SSE reconnection attempts (and noisy logging) after any server-side close or connection failure, and kept trying to reconnect even after unsubscribe. This is a real operational gotcha for long-running services using streaming config updates: an SSE server hiccup turned into a reconnect storm.