-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Chaitanya,
On 7/20/17 11:03 AM, Chaitanya Sabbineni wrote: > Stop script in the sense it's Catalina script only but we usually > stop tomcat using the command Catalina.sh stop. But in our case we > are not manually executing this script to stop tomcat and tomcat is > stopping on its own. > > our main problem here us tomcat is stopping on its own and it needs > a restart. Right. > If I understand you correct you are telling TimerThread that does > not stop when the application is shut down. Can you let me know > what actually the timer thread mean. And moreover if the timer > thread didn't stop ideally tomcat shouldn't stop but in our case > it's stopping. Tomcat is stopping but the JVM is not. If your application were to shut-down cleanly, then the JVM would exit as well. This is unrelated to your real problem (unexpected Tomcat shutdown), but you might want to look into fixing that, because it makes your application impossible to reload without risking serious heap space problems. > Yes my question is why Tomcat is being shut down at all. > > Yes when ever tomcat is stopping on own(not daily) it stops at > 02:00 . You mentioned that your guess is that we are using a > service runner that is configured to bounce your services at > 02:00.Can let me know what this service runner is and how to check > it. I know nothing about your environment. Until you mentioned "catalina.sh stop" above, I didn't even know you were on a UNIX-like environment. Honestly, I assumed you were on Windows because "mysterious service stoppage" has Microsoft Windows behavior written all over it. There are two ways to trigger a Tomcat shut down: 1. Send a TERM signal to the process 2. Connect to Tomcat's shutdown listener (default: port 8005) and give the shutdown command (default: "SHUTDOWN") You can eliminate one of those possibilities by setting the shutdown port in server.xml to "" (empty) which will disable this type of shutdow n: <Server port="" ... You cannot disable the other type of shutdown... any user on the system who can send a TERM signal to your process could terminate Tomcat . As for catching whoever is shutting down your Tomcat, you may want to look at who has administrative access to your server, and who has access to the user running your Tomcat server. Check your syslog to find sudo and cron events that might be automatically shutting-down Tomcat. If you want to catch a TCP connection, you will likely have to enable tcpwrappers, iptables, ipfw, etc. to log connections to port 8005. Those logs will only tell you that the command is being sent, not who is sending it. - -chris -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJZcNOlAAoJEBzwKT+lPKRYsC8QAL14/tZgd/Mg/DXFmGBLXfUh CpCYGPfgEpOLPrEqxbjdpP0172v9tp0+i/DXSJE4kHYUgr3mK0U3Y5Nzyonhttdd yeloPlZfPvVp9VewDd4RlXGda3D/g0r7+6eFXX14Hj1xBVLNitOQ1sRPF/JL9aJS Itjz0q3B6t2ZLIS6sXiOnmMfFjQs986C1R+YVKTkst1l6k+wwyqCPWXCGm/lWLqq MwtTOPq159BGmWqh7T2jHTE/eZ7f81Kzw4mXSh0jPsO3da+2mElzES0LPWoSh3fi 5mkuDUjOqp9OEEPLxkM5HiOEIgy9z0K8WNrSoAKtZpRNezHNmA7zx5rT+rug+aI/ 2GgTBBcPPjuhorO+/IrdneDFpUO3wpcHpkFkoMlqK4e3UaJ5GHByHAF4mn5ssQ38 iQMAwIP7cWtzdEPy0NsjzU7bkMrawNi95U6KDYuZjspz/HEzrgqJKEc4+o3rArVg bd1p8L0PzR3io3Qp9LqnADbEPAbFFSUrj7yqvAdmFTm3bk1A5Z4ljCFnFKI8EG+Z UILGSNovPwKrcyAFcYkdr37xZWObW+BnLtOt8wSuyWr8PDBoTkkMp30KJ+wMXI4P aqnPFdiX88W33LoAIByJ0uDNMnxxyUHVXaWkQ2oGagoJ7DwnK58KredV2peaoeyY GISWZgEaqQxipyI0uZg6 =p4Sz -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
