Hi, So is there an explanation for this? All I am interested is make sure that after a limit, clients attempted to connect are stopped based on my configuration on maxThreads and accept count. But I can not figure out how this works.
________________________________ From: Hermes Flying <flyingher...@yahoo.com> To: Tomcat Users List <users@tomcat.apache.org> Sent: Monday, January 21, 2013 6:17 PM Subject: Re: Fw: Can not understand how maxThreads of Connectors works The web application works.I can not see any issue. What does this mean? ________________________________ From: Mark Thomas <ma...@apache.org> To: Tomcat Users List <users@tomcat.apache.org> Sent: Monday, January 21, 2013 11:06 AM Subject: Re: Fw: Can not understand how maxThreads of Connectors works On 21/01/2013 07:07, Hermes Flying wrote: > > Hi, > Is there any update on this? I don't see any problem setting maxThreads=0 And if you try making a request with a Tomcat instance that uses that configuration? Mark > > Thank you > > > ----- Forwarded Message ----- > From: Hermes Flying <flyingher...@yahoo.com> > To: Tomcat Users List <users@tomcat.apache.org> > Sent: Friday, January 18, 2013 8:55 AM > Subject: Re: Can not understand how maxThreads of Connectors works > > > Hi Chris, > Tried with this simple server.xml and maxThreads=0 but I did not see any kind > of errors.Attached the catalina logs > > <?xml version='1.0' encoding='utf-8'?> > <Server port="8005" shutdown="SHUTDOWN"> > > <!--APR library loader. Documentation at /docs/apr.html --> > <Listener className="org.apache.catalina.core.AprLifecycleListener" >SSLEngine="on" /> > <!--Initialize Jasper prior to webapps are loaded. Documentation at >/docs/jasper-howto.html --> > <Listener className="org.apache.catalina.core.JasperListener" /> > <!-- Prevent memory leaks due to use of particular java/javax APIs--> > <Listener >className="org.apache.catalina.core.JreMemoryLeakPreventionListener" /> > <!-- JMX Support for the Tomcat server. > Documentation at /docs/non-existent.html --> > <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" /> > <Listener >className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" /> > > <!-- Global JNDI resources > Documentation at /docs/jndi-resources-howto.html > --> > <GlobalNamingResources> > <!-- Editable user database that can also be used by > UserDatabaseRealm to authenticate users > --> > <Resource name="UserDatabase" auth="Container" > type="org.apache.catalina.UserDatabase" > description="User database that can be updated and > saved" > factory="org.apache.catalina.users.MemoryUserDatabaseFactory" > pathname="conf/tomcat-users.xml" /> > </GlobalNamingResources> > > <!-- A "Service" is a collection of one or more "Connectors" that share > a single "Container" Note: A "Service" is not itself a "Container", > so you may not define subcomponents such as "Valves" at this level. > Documentation at /docs/config/service.html > --> > <Service name="Catalina"> > > <!--The connectors can use a shared executor, you can define one or more >named thread pools--> > <!-- > > <Executor name="tomcatThreadPool" namePrefix="catalina-exec-" > maxThreads="150" minSpareThreads="4"/> > --> > > > <!-- A "Connector" represents an endpoint by which requests are received > and responses are returned. Documentation at : > Java HTTP Connector: /docs/config/http.html (blocking & non-blocking) > Java AJP Connector: /docs/config/ajp.html > APR (HTTP/AJP) Connector: /docs/apr.html > Define a non-SSL HTTP/1.1 Connector on port 8080 > --> > <Connector port="8080" maxThreads="0" acceptCount="1" > protocol="HTTP/1.1" > connectionTimeout="20000" > redirectPort="8443" /> > > <!-- Define an AJP 1.3 Connector on port 8009 --> > <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" /> > > > <!-- An Engine represents the entry point (within Catalina) that processes > every request. The Engine implementation for Tomcat stand alone > analyzes the HTTP headers included with the request, and passes them > on to the appropriate Host (virtual host). > Documentation at /docs/config/engine.html > --> > > <!-- You should set jvmRoute to support load-balancing via AJP ie : > <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1"> > --> > <Engine name="Catalina" defaultHost="localhost"> > > > <!-- This Realm uses the UserDatabase configured in the global JNDI > resources under the key "UserDatabase". Any edits > that are performed against this UserDatabase are immediately > available for use by the Realm. --> > <Realm > className="org.apache.catalina.realm.UserDatabaseRealm" > resourceName="UserDatabase"/> > > <!-- Define the default virtual host > Note: XML Schema validation will not work with Xerces 2.2. > --> > <Host name="localhost" appBase="webapps" > unpackWARs="true" autoDeploy="true" > xmlValidation="false" xmlNamespaceAware="false"> > > > </Host> > </Engine> > </Service> > </Server> > > > > > > > > ________________________________ > From: Christopher Schultz <ch...@christopherschultz.net> > To: Tomcat Users List <users@tomcat.apache.org> > Sent: Thursday, January 17, 2013 6:57 PM > Subject: Re: Can not understand how maxThreads of Connectors works > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > André, > > On 1/17/13 3:32 AM, André Warnier wrote: >> Quite a few messages ago, I asked the OP if he could copy/paste >> his server.xml. > > Yes. Getting information from the OP seems to be difficult. > >> The reason was that if his config uses an Executor, then I believe >> the Threads settings in the Connectors don't really matter, do they >> ? > > Correct: setting executor="someExecutor" means that any > executor-related settings on the <Connector> will be ignored in favor > of those set in the <Connector>. > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEAREIAAYFAlD4LX4ACgkQ9CaO5/Lv0PAzegCgtxrX5Yx2V0UlEiDI1hK/vK+H > u20AmwWQz6+LToA3uPSSb8V1+kdPMY3N > =9fQb > -----END PGP > SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
