-
Notifications
You must be signed in to change notification settings - Fork 784
Jetty fails with IllegalStateException on hosts with many cores #6574
Comments
Do you happen to know how Jetty calculates the minimal number based on the cores? |
I tracked it as far as here, but didn't get to the actual calculation. |
What is weird is that the exception says I checked the code and it seems we are not mixing up min&max anywhere. So I have no idea, why it thinks that max should be limited to 10...? |
Yeah that had me scratching my head too. 😕 I just did a test on my 6-core box. With these settings
I got this exception. So for some reason could it be using the
|
And, I just changed |
The bug seems to be here: It invariably creates and sets a new ThreadPool with |
The threadpool that is created here does not ever seem to be used :-( |
Ugh. I can't believe I didn't spot that when reading through the code. |
#6588 shoud fix it. |
Thanks! So, now that it's using the correct max of 40, the likelihood of throwing that error becomes greatly reduced, except if the host has a lot of cores. |
Right and if you are running such a massively parallel machine, you are still free to add an individual configuration for the pool size. |
Yep. While the likelihood of someone running into this is now very low, I'll update my forum post to be more explicit about which parameter needs to be changed. |
On hosts with many cores (somewhere around 16 or more), Jetty throws an IllegalStateException when starting up. As the webclient config parameters are buried in the code, there's no obvious way to figure out how to work around the problem (other than finding my post on the forum).
The text was updated successfully, but these errors were encountered: