Solution skill
Kameleoon Java SDK hammered the server with SSE reconnects after a server-side close
Complete solution
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.
Kameleoon Java SDK hammered the server with SSE reconnects after a server-side close
TL;DR
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. 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.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
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.
Evidence
Source: 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.
Verified resolution: 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.
Source URL: https://github.com/kameleoon-new/client-java/blob/HEAD/CHANGELOG.md#4242---2026-09-14
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_ns6q20dScZK_gDVIHQlHrg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Kameleoon Java SDK hammered the server with SSE reconnects after a server-side close <span>— Vectle</span></a>