-
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
Starting HttpClient with destinationIdleTimeout set throws NPE. #8753
Labels
Bug
For general bugs on Jetty side
Comments
janvojt
added a commit
to janvojt/jetty.project
that referenced
this issue
Oct 21, 2022
janvojt
added a commit
to janvojt/jetty.project
that referenced
this issue
Oct 21, 2022
…Timeout set. Signed-off-by: Jan Vojt <jan@vojt.net>
janvojt
added a commit
to janvojt/jetty.project
that referenced
this issue
Oct 21, 2022
…Timeout set. Signed-off-by: Jan Vojt <jan@vojt.net>
janvojt
added a commit
to janvojt/jetty.project
that referenced
this issue
Oct 21, 2022
…Timeout set. Signed-off-by: Jan Vojt <jan@vojt.net>
janvojt
added a commit
to janvojt/jetty.project
that referenced
this issue
Oct 21, 2022
…Timeout set. Signed-off-by: Jan Vojt <jan@vojt.net>
sbordet
added a commit
that referenced
this issue
Oct 22, 2022
…on-idle-timeout Issue #8753 - Fix HttpClient initialization with destinationIdleTimeout set.
Fixed by #8756. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version(s)
>= 11.0.x
Java version/vendor
(use: java -version)
any
OS type/version
any
Description
If
HttpClient
is initialized with a default (implicit) scheduler and at the same timedestinationIdleTimeout
is set, thenHttpClient
cannot start and throwsNullPointerException
.How to reproduce?
Throws:
The text was updated successfully, but these errors were encountered: