feat(java): implement connection pooling for AsyncTcpConnection (… #2574
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR implements connection pooling for the
AsyncTcpConnectionin the Java SDK, resolving issue #2232.Previously, the async client used a single connection, which could lead to bottlenecks. This implementation introduces a configurable pool (using Netty's
FixedChannelPool) to improve throughput and reliability.Key Changes
FixedChannelPoolintoAsyncTcpConnection.TCPConnectionPoolConfigto allow configuration of:PoolMetricsto track:sendAsyncto acquire channels from the pool and release them back upon completion (or failure).CompletableFuturecancellation and channel health checks.Issue Link
Closes #2232
Checklist