Netty default maxconnections

[srnagar]

Description

reactor-netty uses different default values for maxConnections and pendingAcquireMaxCount when a HttpClient instance is created with and without a ConnectionProvider.

HttpClient.create() uses 500 connections (called when HttpClientOptions is not set)
HttpClient.create(ConnectionProvider) uses maxAvailableProcessors * 2 (minimum of 16) (called when HttpClientOptions is set).

pendingAcquireMaxCount is 2x the maxConnections if not explicitly set.

This difference in defaults can lead to issues like this - #26027

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes. (but disabled due to a bug in reactor-netty)

[alzimmermsft]

So, is this a bug in Reactor Netty or a design decision?