-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
QoSFilter.setMaxRequests throws NullPointerException #7414
Labels
Bug
For general bugs on Jetty side
Comments
@bu3 thanks for the report we'll take a look. In the meanwhile, as a workaround, I note that all our unit tests set these properties by calling FilterHolder holder = new FilterHolder(QoSFilter.class);
holder.setInitParameter(QoSFilter.MAX_REQUESTS_INIT_PARAM, x); |
Nice! I will give it a try. Thanks a million @janbartel |
janbartel
added a commit
that referenced
this issue
Feb 1, 2022
Signed-off-by: Jan Bartel <[email protected]>
janbartel
added a commit
that referenced
this issue
Feb 7, 2022
janbartel
added a commit
that referenced
this issue
Feb 8, 2022
* Issue #7414 Deprecate QoSFilter setters Signed-off-by: Jan Bartel <[email protected]>
joakime
pushed a commit
that referenced
this issue
Feb 25, 2022
* Issue #7414 Deprecate QoSFilter setters Signed-off-by: Jan Bartel <[email protected]> (cherry picked from commit c742c2e)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version(s)
9.4.44
Java version/vendor
(use: java -version)
openjdk version "11.0.10" 2021-01-19 LTS
OS type/version
macOS 11.6.2
Description
I'm trying to use the QosFilter into an existing Spring application but if I try to tune the filter calling
setMaxRequests
at configuration time, it throws the following NullPointer exception:this is the code I'm using to create a Spring Bean with the QosFilter:
I think it blows up because
QosFilter.init()
method has not been called yet at that stage and the private property_passes
is null here.How to reproduce?
@Configuration
annotated classThe text was updated successfully, but these errors were encountered: