On Fri, Oct 2, 2009 at 09:50, Jerome Louvel <[email protected]> wrote:
> This only affect the Jetty connector, but this is annoying indeed. Note that > we do fallback on the default (255) value in this case. Thanks for taking this seriously. I actually think it's more than annoying — 255 threads might be OK for an app running on a dedicated 8-core machine, but many apps run on shared servers, with only 1-4 cores. And of course it depends greatly on what those requests are doing. If handling them requires any lengthy and/or intensive work, handling 255 requests simultaneously could hang or crash the service, or maybe even the entire machine, or at least lock it up for a long time, similar to a DOS situation. This is actually occurring for me in one of my important production apps, but I can't blame it on the bug exactly — I just forgot to set the parameter in my code! Still, the situation I'm experiencing makes clear, to me, the severity of this bug. > I'm currently planning on releasing 1.1.7 in sync with Restlet 2.0 M6, in > about one month. I'd like to fix a couple more bugs pending on 1.1 branch: > http://www.restlet.org/about/roadmap Sounds good! ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2402938
