I'm using the APR Connector.
Here's my server.xml:
<?xml version='1.0' encoding='utf-8'?>
<Server port="8005" shutdown="SHUTDOWN">
<Listener className="org.apache.catalina.core.AprLifecycleListener"
SSLEngine="on" />
<Listener className="org.apache.catalina.core.JasperListener" />
<Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
/>
<GlobalNamingResources>
<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" />
<Resource name="mail/Session" auth="Container"
type="javax.mail.Session"
mail.smtp.host="localhost"/>
</GlobalNamingResources>
<Service name="Catalina">
<Connector port="8080" protocol="HTTP/1.1" URIEncoding="utf-8"
maxKeepAliveRequests="3" keepAliveTimeout="3000"
redirectPort="8443" />
<Connector port="8443" URIEncoding="utf-8"
maxKeepAliveRequests="3" keepAliveTimeout="3000"
scheme="https" secure="true" SSLEnabled="true"
SSLCertificateFile="/home/user/ssl/2010.www.surfcanyon.com.crt"
SSLCertificateKeyFile="/home/user/ssl/www.surfcanyon.com.key"
SSLCertificateChainFile="/home/user/ssl/intermediateCA.cer"
clientAuth="false" sslProtocol="TLS"/>
<Engine name="Catalina" defaultHost="localhost">
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>
<Host name="localhost" appBase="webapps" unpackWARs="true"
autoDeploy="true">
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="%I %t %U %T" resolveHosts="false"/>
</Host>
</Engine>
</Service>
</Server>
On Sat, Dec 31, 2011 at 5:39 AM, Pid <p...@pidster.com> wrote:
> On 30/12/2011 02:01, Mike Wertheim wrote:
>> I have an app that runs on Tomcat 7.0.21 and APR 1.4.7 just fine. The
>> app serves both SSL and non-SSL traffic. SSL traffic makes up roughly
>> 1% of the overall traffic. The Connectors for SSL and non-SSL both
>> use the default value (200) for maxThreads.
>>
>> When I try to run the app on Tomcat 7.0.23 (with the same server.xml,
>> context.xml and web.xml) and APR 1.4.7, the app slowly grinds to a
>> halt after running on a live production server for about a day.
>>
>> I took heap dumps of the app on both 7.0.21 and 7.0.23 and don't see
>> any significant difference in memory usage. Memory seems to be fine.
>>
>> I did a stack dump on 7.0.23 when it was in its messed up state. No
>> threads are blocked on critical sections of my app.
>>
>> For the port 8080 connector, there are 196 threads in "waiting on
>> condition" and 4 threads in "runnable".
>>
>> For the port 8443 connector, there are 81 threads in "waiting on
>> condition" and 119 threads in "runnable".
>>
>> I don't know how to interpret this data, since I'm not really clear on
>> what the difference is between "runnable" and "waiting on condition".
>> Do these numbers seem normal, or are they perhaps giving a clue as to
>> what the underlying problem might be?
>
> Which Connector are you using?
>
> Can you please remove the XML comments and obscure username/password/ip
> addresses if applicable in your server.xml and then post it inline here?
>
>
> p
>
> --
>
> [key:62590808]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
