I did not stop the server and copied a war file into it causing tomcat service to be in a hung state. The odd thing is that the new service worked fine whereas the old one stopped working.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I did not stop the server and copied a war file into it causing tomcat service to be in a hung state. The odd thing is that the new service worked fine whereas the old one stopped working.
Tomcat may hang when you upgrade an existing WAR and one the libraries of the old WAR file has been locked and cannot be unloaded. You can see it by the exploded folder of the old WAR being almost empty, expect of one or more JAR files in
/WEB-INF/lib. You see this very often with JavaMail’smail.jaron Windows based JVM’s.A solution to that is to set the
antiResourceLockingattribute of the webapp’s<Context>element totrue. Also see Tomcat Configuration Reference – The Context Container.