Skip to content

Fix/entity verticle fqn proxy send timeout - #802

Merged
ikalachy merged 3 commits into
mainfrom
fix/entity-verticle-fqn-proxy-send-timeout
Sep 8, 2026
Merged

Fix/entity verticle fqn proxy send timeout#802
ikalachy merged 3 commits into
mainfrom
fix/entity-verticle-fqn-proxy-send-timeout

Conversation

@ikalachy

@ikalachy ikalachy commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

No description provided.

The FQN consumer (EntityVerticle[<FQN>]) forwards requests to the
co-located DataVerticle[<name>] instance with a freshly constructed
DeliveryOptions that did not set a send timeout, so the inner hop fell
back to Vert.x's hardcoded 30s default reply timeout instead of the
configured eventBusTimeout. Since b12652b made requests reliably route
through this proxy (local-preferred resolution), any retrieveData taking
longer than 30s but within the configured budget was abandoned after 30s
with (RECIPIENT_FAILURE,-1) Timed out after 30000(ms), surfacing as HTTP
500.

The inner hop now inherits the configured eventBusTimeout.

Adds EntityVerticleTimeoutClusterTest (FakeClusterManager, CI-safe): with
eventBusTimeout=40s and a reply delayed 33s it fails on the old code (30s
timeout on the inner hop) and passes with the fix.
@ikalachy
ikalachy requested a review from a team as a code owner September 8, 2026 11:36
@ikalachy
ikalachy merged commit a5e53b4 into main Sep 8, 2026
7 checks passed
@ikalachy
ikalachy deleted the fix/entity-verticle-fqn-proxy-send-timeout branch September 8, 2026 12:30
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