> From: Timir Hazarika [mailto:timir.hazar...@gmail.com] > Subject: Tomcat does not honor acceptCount configuration variable > > What is the best way to limit connections in tomcat, if there is one ?
Somewhat depends on what you think "connection" means. If you're actually referring to sessions, you'll have to limit that based on logic in your webapp, usually implemented in an HttpSessionListener (read the servlet spec for how to configure one). > I have tried acceptCount The acceptCount is the value used by the platform's TCP/IP stack to limit the number of HTTP connection requests held in a queue. The number actually in the queue at any given time is invisible to Tomcat. > maxThreads The maxThreads settings limits the number of requests that Tomcat will handle concurrently. For the JIO <Connector>, that's also the number of active HTTP connections using keep-alive, since there's a thread dedicated to each active connection. For the NIO and APR connectors, threads are not dedicated to HTTP connections, so it's purely the concurrent request limit. > explicit executor This is simply a way of sharing a thread pool across multiple <Connector> elements, nothing more. So what exactly are you trying to limit? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org