why not start by creating a backup copy of your server.xml, and then removing all of the commented out config.
it'll be easier to see what's going on that way... p connossieur wrote: > I realize that my Server.xml is not being used by the Tomcat engine. I mean > the Connector part. > Should I make any modifications anywhere? > > And I regret for the last repeated mails. It was sent by mistake. > -Anand > > connossieur wrote: >> Christopher, >> >> This is my Server.xml >> <!-- Note: A "Server" is not itself a "Container", so you may not >> define subcomponents such as "Valves" at this level. >> Documentation at /docs/config/server.html >> --> >> <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" /> >> <!-- 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"> >> >> <!-- 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 >> --> >> <Executor name="tomcatThreadPool" namePrefix="catalina-exec-" >> maxThreads="70" minSpareThreads="20"/> >> <Connector executor="tomcatThreadPool" >> port="80" protocol="HTTP/1.1" >> connectionTimeout="2000" >> redirectPort="8443" /> >> <!-- <Connector port="8080" protocol="HTTP/1.1" >> maxThreads="150" connectionTimeout="20000" >> redirectPort="8443" /> --> >> >> <!-- Define a SSL HTTP/1.1 Connector on port 8443 >> This connector uses the JSSE configuration, when using APR, the >> connector should be using the OpenSSL style configuration >> described in the APR documentation --> >> <!-- >> <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" >> maxThreads="150" scheme="https" secure="true" >> clientAuth="false" sslProtocol="TLS" /> >> --> >> >> <!-- 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="Standalone" defaultHost="localhost" jvmRoute="jvm1"> >> >> --> >> <Engine name="Catalina" defaultHost="localhost"> >> >> <!--For clustering, please take a look at documentation at: >> /docs/cluster-howto.html (simple how to) >> /docs/config/cluster.html (reference documentation) --> >> <!-- >> <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/> >> --> >> >> <!-- The request dumper valve dumps useful debugging information >> about >> the request and response data received and sent by Tomcat. >> Documentation at: /docs/config/valve.html --> >> <!-- >> <Valve className="org.apache.catalina.valves.RequestDumperValve"/> >> --> >> >> <!-- 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"> >> >> <!-- SingleSignOn valve, share authentication between web >> applications >> Documentation at: /docs/config/valve.html --> >> <!-- >> <Valve className="org.apache.catalina.authenticator.SingleSignOn" >> /> >> --> >> >> <!-- Access log processes all example. >> Documentation at: /docs/config/valve.html --> >> <!-- >> <Valve className="org.apache.catalina.valves.AccessLogValve" >> directory="logs" >> prefix="localhost_access_log." suffix=".txt" >> pattern="common" resolveHosts="false"/> >> --> >> >> </Host> >> </Engine> >> </Service> >> </Server> >> >> Do you think this has a problem? I'll try to upload the thread Dump to my >> website and send a link. >> >> Anand >> >> >> Christopher Schultz-2 wrote: > Stephen, > > On 4/21/2009 5:35 PM, Stephen Caine wrote: >>>>> This is the number of threads Tomcat will handle before it errors with >>>>> 'max threads reached. This is on OS X, 64 bit memory. The heap size is >>>>> 2 gigs. >>>>> >>>>> If you know how to increase this number, then please provide the >>>>> information. Others have also noted this limit on OS X in previous >>>>> posts to this list. > ulimit? > > On my Mac OS X 10.4.11, "ulimit -a" reports max user processes (-u > switch) are set to 256. You could probably increase that by doing: > > ulimit -u 1024 > > or whatever. If you've reached an upper limit of 2400, it's probably > because you're reaching a hard limit set up somewhere else. > > There's also: > > sysctl -w kern.maxprocperuid=1024 (or more?) > or > sysctl -w kern.maxproc=10000 (or more?) > > (My kern.maxproc is currently set to 532 -- what a strange number -- > while kern.maxprocperuid is currently 266). > > You can also set your defaults in /etc/sysctl.conf: > > kern.maxproc=10000 > kern.maxprocperuid=5000 > > I didn't know any of this before 5 minutes ago. Google is your friend. > > -chris >>> --------------------------------------------------------------------- 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
