Implement HTTP connection pooling for WxPayServiceApacheHttpImpl #3648
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.
This PR implements HTTP connection pooling for
WxPayServiceApacheHttpImpl
to address performance issues caused by creating new HttpClient instances for each request.Problem
The current implementation creates a new
HttpClient
for every HTTP request:This approach causes:
Solution
Implemented connection pooling using Apache HttpClient's
PoolingHttpClientConnectionManager
:Key Changes
Added connection pool configuration to WxPayConfig:
maxConnTotal
(default: 20) - Maximum total connectionsmaxConnPerRoute
(default: 10) - Maximum connections per routeEnhanced WxPayConfig with pooled client initialization:
Modified request methods to use pooled clients:
Features
HttpClientBuilderCustomizer
interfacePerformance Benefits
Usage
Connection pooling is automatically enabled with sensible defaults:
Fixes #3640.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.