Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

modify the default value to avoid breaking changes of http client #26062

Conversation

yiliuTo
Copy link
Member

@yiliuTo yiliuTo commented Dec 16, 2021

Modify the default value of maximumConnectionPoolSize as 500, which is to keep the same default behaviour with reactor netty client and avoid breaking changes with our previous versions.
Ref: https://projectreactor.io/docs/netty/snapshot/reference/index.html#_connection_pool_2

@ghost ghost added the azure-spring All azure-spring related issues label Dec 16, 2021
Comment on lines +73 to +76
AzureEventHubsProperties properties = context.getBean(AzureEventHubsProperties.class);
Integer maximumConnectionPoolSize =
properties.getProcessor().getCheckpointStore().getClient().getMaximumConnectionPoolSize();
assertEquals(maximumConnectionPoolSize, 500);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest we add a separate test case here.

@yiliuTo yiliuTo added azure-spring-eventhubs Spring event hubs related issues. Client This issue points to a problem in the data-plane of the library. labels Dec 21, 2021
@yiliuTo yiliuTo added this to the Spring Cloud Azure 4.0 GA milestone Dec 21, 2021
@yiliuTo
Copy link
Member Author

yiliuTo commented Dec 21, 2021

Close this pr for this has been fixed at the SDK side via #26083, and it will take effect after the version of 1.12.0 of azure-core-http-netty being released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
azure-spring All azure-spring related issues azure-spring-eventhubs Spring event hubs related issues. Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants