> -----Original Message----- > From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Sent: Monday, March 10, 2014 11:22 AM > To: Tomcat Users List > Subject: Re: Executor thread pool > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > John, > > On 3/10/14, 11:43 AM, John Smith wrote: > > How dumb am I being by not using an Executor with a named thread > pool? > > Currently I just have a Connector in server.xml: > > > > <Connector port="8080" > > protocol="org.apache.coyote.http11.Http11NioProtocol" > > connectionTimeout="20000" redirectPort="8443" /> > > An executor is being used under the covers... you just aren't > configuring it yourself. > > If you don't configure it yourself you lose out on these benefits: > > 1. Shared executor for multiple Connectors. If you only have a single > connector, obviously this matters little. > > 2. You have less control over the underlying Executor if you don't > manually configure it and let the Connector auto-create one. Check the > documentation for http://tomcat.apache.org/tomcat-7.0- > doc/config/executor.html against the thread-related configuration > attributes available for, say, the HTTP connector here > http://tomcat.apache.org/tomcat-7.0-doc/config/http.html and you'll see > what I mean. > > > Assuming ~2000 simultaneous connections. Tomcat 7.0.42. RHEL6. > > 2000 simultaneous connections really is quite a lot. Are you sure? > 2000 simultaneous sessions isn't a stretch, but 2k connections is a big > deal. How long are your transactions? What is the incoming request > rate? >
How about the more likely 2 connector scenario, one for port 80 one for port 443? Any benefit of using the executor here? Assuming sharing one between connectors, and web.xml configured to auto-route everything to SSL, i.e. time spent on 80 is minimal (redirect)? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
