The exact timestamp 021645 corresponded to a production incident where over 2,000 concurrent subscriptions timed out within one minute. The fix was rolled out as patch version dass341-hotfix-021645 . The changes included: 3.1 Code Change (Java) Before (buggy):
public void subscribe(String topic) CompletableFuture<Ack> future = broker.subscribe(topic); try Ack ack = future.get(5000, TimeUnit.MILLISECONDS); catch (TimeoutException e) retrySubscribe(topic); // dangerous: no rate limit log.error("javxsubcom021645: min ack timeout"); dass341 javxsubcom021645 min fixed
Additionally, the team updated the application.yml : The exact timestamp 021645 corresponded to a production
| Test | Load | Result | |------|------|--------| | Unit test | 100 concurrent subs | No timeout errors | | Integration | 5000 subs over 5 min | Max 2 retries per sub | | Canary prod | 10% traffic, 02:16:45 replay | No javxsubcom021645 logs | the team ran three validation steps:
dass: subscription: min-ack-ms: 5000 max-retries: 3 retry-backoff-ms: 1000 The “min fixed” refers to setting a (1 second) and a maximum retry cap (3 attempts), preventing retry storms. 4. Testing and Validation After deploying the fix, the team ran three validation steps: