-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Métairie,
On 11/25/14 7:47 AM, Métairie, Stéphane wrote:
> Sorry it's not tomcat7 but tomcat6
>
> Tomcat Version : Apache Tomcat/6.0.24 Servlet Specification Version
> : 2.5 JSP version : 2.1
>
> java version "1.7.0_21" Java(TM) SE Runtime Environment (build
> 1.7.0_21-b11) Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01,
> mixed mode)
>
>
> Server.xml <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.core.JreMemoryLeakPreventionListener"
> /> <Listener
> className="org.apache.catalina.mbeans.ServerLifecycleListener" />
> <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" /> </GlobalNamingResources>
> <Service name="Catalina"> <Connector port="8080"
> protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443"
> /> <Connector port="8009" protocol="AJP/1.3" redirectPort="8443"
> /> <Engine name="Catalina" defaultHost="localhost"> <Realm
> className="org.apache.catalina.realm.UserDatabaseRealm"
> resourceName="UserDatabase"/> <Host name="localhost"
> appBase="webapps" unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false"> <Valve
> className="org.apache.catalina.valves.AccessLogValve"
> directory="logs" prefix="localhost_access_log." suffix=".txt"
> pattern="%t resp[%s] [%a] spentTime[%D] '%r' - bytes[%b]
> thread[%I]" resolveHosts="false"/> </Host> </Engine> </Service>
> </Server>
>
> Tomcat6.conf CATALINA_BASE="/usr/share/tomcat6"
> CATALINA_HOME="/usr/share/tomcat6"
> JASPER_HOME="/usr/share/tomcat6"
> CATALINA_TMPDIR="/var/cache/tomcat6/temp" JAVA_OPTS="${JAVA_OPTS}
> -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory
> -server -Xms1024m -Xmx1024m -XX:NewSize=512m -XX:MaxNewSize=512m
> -XX:PermSize=512m -XX:MaxPermSize=512m"
> CATALINA_OPTS="${CATALINA_OPTS} -Dcom.sun.management.jmxremote
> -Dcom.sun.management.jmxremote.port=9999
> -Dcom.sun.management.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false" TOMCAT_USER="tomcat"
> SECURITY_MANAGER="false" SHUTDOWN_WAIT="30" SHUTDOWN_VERBOSE=false
> CATALINA_PID="/var/run/tomcat6.pid"
>
>
> -----Original Message----- From: André Warnier
> [mailto:a...@ice-sa.com] Sent: mardi 25 novembre 2014 13:33 To:
> Tomcat Users List Subject: Re: tomcat7 shutdown himself without
> trace
>
> Métairie wrote:
>> Hi all
>>
>> We have a tomcat7 standalone in Redhat6.
>>
>> Sometime the Tomcat7 suddenly stop to reply to all requests, but
>> all server parameters are ok (cpu, memory, disk, ... all are ok).
>> There is no error inside the logs. No exception, nothing.
>>
>> The http-thread do not reply anymore, because the pool is fallen
>> to a minimum to 5 or 6 threads. I guess all http-thread are
>> killed without any reason.
>>
>
> Can you paste the server.xml file here ? (Remove all comments,
> domain names and other confidential information if any)
>
> To save time for everyone in the long run, can you also provide : -
> the exact version of Tomcat used (7.y.z) - the JVM version used
>
> (You should be able to see all that by going to the Tomcat bin
> directory and executing "version.sh")
>
> There may be a reason for the Tomcat threads disappearing : if the
> minimum you set in the configuration is the above 5-6, and if the
> threads have nothing to do (Tomcat does not receive any requests
> anymore, due to some network issue e.g.) then the threads would
> "naturally" die, and Tomcat would not necessarily start new ones to
> replace them, since there is no need to.
>
> Also maybe helpful : when the case occurs (Tomcat not responding),
> run the command : netstat -pan --tcp and check if anything unusual
> appears there (like hundreds of connections to the Tomcat HTTP
> port, in some unexpected state).
When disaster strikes, is the JVM process still running, or is the
process completely gone?
Does the Tomcat log say anything about it trying to shut down?
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJUdPTpAAoJEBzwKT+lPKRYNMEP/2DXRJAhiYz205iXYx5HkZE3
xU0RIMdT7AF1C4afSQM40aeFJswITlcTdAGxiGoRRh6Ubimyl6r7f+bd+hdQflYP
d65QUy11JfshDT4vyHjxEhZTCG8aDQ3dJcQBGOpbe/Lx7s8SgrLIk8TzJRiBalLc
QAwnm8K1A2aWcTIrnxO5G4S4/n/QYsL65un0hTOmy5RygGHRdgVQt47mz6wSDKiv
KH4kD8cdjyBtIGUHpxzqwsDWuEOOvv3xLnvktpPKNDzB46E42J8lT89MJOECj9/R
IJIhdStfB2EWQ26AYBHd1X8vDe2Lp3uLj3ZQzGfNivaceN/5GVYgCf/NqrI4+/pd
ihx4isu3xTXt6dYOf3aLCzFR5LzVUSrt207OwXJaOC+0kl7Jgv7liXYaOEF0KqAf
3jEy/7ZBToZwwl/YSebbkqWvDEfM/IhpkbQVOvgAatmLCY7f6aGmTt116hQ8j14z
W+Z/9CT3Qmc5qGtQfki/wkc9bsKPgHiaifdaW+acLBPvUC5oOoO02wU8ujPPG0Zw
oJd8+Pnxc6/LndaVl3AqRBzHV4OL1cAH1cnnIguGVzew/fV1Mq+NFBlho7hIkBfb
UhlSgwi6CDsyG6XJG6XCWIJ5452g/fFOnD8UC6XYVSusCflsMEXRfaD7tIi9KqtO
nYOvgxNpIC65QFeiIIF0
=t9jE
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
