Jon,
Try using an <Executor>. You are using a non-nuanced configuration and
will therefore get inflexible threading behavior.
Thanks,
-chris
On 9/20/22 02:47, Jonathan Yom-Tov wrote:
hi Christopher,
Configuration follows:
<?xml version="1.0" encoding="UTF-8"?>
<Server port="-1" shutdown="SHUTDOWN">
<Listener className="org.apache.catalina.startup.VersionLoggerListener" />
<!-- Security listener. Documentation at /docs/config/listeners.html
<Listener className="org.apache.catalina.security.SecurityListener" />
-->
<!-- APR library loader. Documentation at /docs/apr.html -->
<Listener className="org.apache.catalina.core.AprLifecycleListener"
SSLEngine="on" />
<!-- Prevent memory leaks due to use of particular java/javax APIs-->
<Listener
className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
<Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
<Listener
className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />
<Service name="Catalina">
<Connector port="20420" URIEncoding="UTF-8" protocol="HTTP/1.1"
connectionTimeout="20000" redirectPort="8443" maxHttpHeaderSize="8192"
scheme="https" secure="true" proxyPort="443" server="serverName"
relaxedQueryChars=" { } " />
<Connector port="2042" URIEncoding="UTF-8" protocol="HTTP/1.1"
relaxedQueryChars=" { } "
connectionTimeout="20000"
redirectPort="8443" maxHttpHeaderSize="8192" />
<Engine name="Catalina" defaultHost="localhost" jvmRoute="someRoute">
<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= "%t %h:%{remote}p %{communityUserName}c %S %u
%{Host}i %r %s %b %{Referer}i %{User-Agent}i %{Authorization}i **%T/%D**
%{X-Cluster-Client-IP}i" />
<Context path="" docBase="/some/path" debug="0"/>
<Valve
className="com.sysaid.session.persistence.PeriodicPersistingValve"
persistIntervalSeconds="20" enabled="true" />
<Valve
className="org.apache.catalina.valves.StuckThreadDetectionValve"
threshold="120" />
<Valve className="org.apache.catalina.valves.ErrorReportValve"
showReport="false" showServerInfo="false" />
</Host>
</Engine>
</Service>
</Server>
On Mon, Sep 19, 2022 at 7:45 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
Jon,
On 9/19/22 10:46, Jonathan Yom-Tov wrote:
Sometimes one of our production Tomcats will start with the maximum (200)
number of threads in the https pool. That is, it doesn't start with some
minimum and works its way up to the maximum, it immediately starts with
the
maximum. There's no reason for it since most of the threads stay idle
through the lifetime of the Tomcat. The issue is that this takes up
memory
and eventually something pushes the Tomcat over the edge and it dies with
an out of memory error. Any ideas on how to debug or solve this?
The Tomcat version is 9.0.64.0, running on Amazon Linux 2 (amd64) and
Java
Corretto 1.8.0_312-b07.
Can you post your configuration?
-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
