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.

Sign up for GitHub

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

Jump to bottom

jetty-lowresources.xml and lowresources.mod still refer to deprecated and removed setMaxConnections #8174

Closed
joakime opened this issue Jun 16, 2022 · 1 comment · Fixed by #8175
Closed

jetty-lowresources.xml and lowresources.mod still refer to deprecated and removed setMaxConnections #8174

joakime opened this issue Jun 16, 2022 · 1 comment · Fixed by #8175
Labels
Bug For general bugs on Jetty side Sponsored This issue affects a user with a commercial support agreement

Comments

@joakime
Copy link
Contributor

joakime commented Jun 16, 2022

Jetty version(s)
10+

Java version/vendor (use: java -version)
All

OS type/version
All

Description

When using lowresources module, the maxConnections setter throws an error if you attempt to use it, as the methods were deprecated in Jetty 9.4.x and removed in Jetty 10.0.0.
(Replaced by connectionlimit module)

The removal didn't remove the XML and MOD references though.
@joakime joakime added Bug For general bugs on Jetty side Sponsored This issue affects a user with a commercial support agreement labels Jun 16, 2022
@joakime joakime mentioned this issue Jun 16, 2022
Merged
@joakime
Copy link
Contributor Author

joakime commented Jun 16, 2022

Opened PR #8175

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug For general bugs on Jetty side Sponsored This issue affects a user with a commercial support agreement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Removing invalid maxConnections references jetty/jetty.project
1 participant
@joakime