apache / apache/servicecomb-java-chassis
[BUG] - Java-Chassis3.2.1之后版本servicecomb.rest.client下的connection.maxPoolSize、http2.maxPoolSize、maxWaitQueueSize等配置项失效，只能使用固定默认值
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 814
- Avg merge
- 8d 23h
- Merged PRs (30d)
- 1
Description
### Steps to Reproduce
Java-Chassis3.2.1 版本引入修改，创建HttpClient时原本使用 `xxx.createHttpClient(httpClientOptions)`, 修改为使用 `xxx.with(httpClientOptions)`
而`xxx.with(httpClientOptions)`只设置了`HttpClientOptions`
原本`xxx.createHttpClient(httpClientOptions)` 预期为同时修改`HttpClientOptions` 与 `PoolOptions`
导致在后续buildHttpClient时，`this.poolOptions`一直都为null，所以都是使用的默认`PoolOptions`
### Expected Behavior
预期只需要修改把`poolOptions`设置进去即可
### Servicecomb Version
_No response_
### Additional Context
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Trace the Java-Chassis3.2.1 change from createHttpClient(httpClientOptions) to with(httpClientOptions), then follow buildHttpClient and the HttpClientOptions and PoolOptions handling. Verify that connection.maxPoolSize, http2.maxPoolSize, and maxWaitQueueSize reach PoolOptions rather than default values, and add or run a regression test for those settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100