Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Lockup in jetty-client under low threads / slow destination condition

Thank you for the information on the constraint; I will increase threads to 6 and continue attempts to reproduce the original problem report.

In the scenario there are two HttpClient instances each sharing the same pool. Each HttpClient has a transport configured with 2 selectors. The commit that put the selector configuration in there appears to have been intended to reduce the number of selectors from Jetty's default of half the available processors.



Back to the top