Christopher, thanks for this information, but Tullio said that his problem only occurs with the NIO connector (it seems weird and I don't have sufficient knowledge on how it is coded in Tomcat anyway).
The post was already quite long before I suggested him to try both connectors to identify a possible problem there. I'm just being pragmatic here. 2016-03-09 16:41 GMT+01:00 Christopher Schultz <ch...@christopherschultz.net >: > Aurélien, > > On 3/9/16 8:50 AM, Aurélien Terrestris wrote: > > The doc ( > > > http://tomcat.apache.org/tomcat-8.0-doc/config/http.html#NIO2_specific_configuration > > ) doesn't say which one is the best, but we may think that the > non-blocking > > will work better under heavy load. > > NIO2 is newer and has had less testing in the wild. Between the two I'd > stick to NIO. > > > If not servicing hundreds of clients at the same moment, I would use the > > blocking connector ( http11.Http11Protocol ) > > Note that the blocking connector doesn't work well with asynchronous > protocols like websocket, etc. It is being removed from Tomcat in Tomcat > 9. (RIP BIO) > > -chris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >