S Arvind wrote: > Thanks pid... > > Can u able to give me more idea to solve it if possible..
Did you write your application? Are you using Quartz in your application? Are you starting new Threads in your app? When you have started and stopped the application a few times are there still multiple java processes running? p > Thanks, > Arvind S > > > *"Many of lifes failure are people who did not realize how close they were > to success when they gave up." > -Thomas Edison > * > > On Sat, Apr 25, 2009 at 2:00 PM, Pid <p...@pidster.com> wrote: > >> S Arvind wrote: >>> A wierd problem occur while shutdowning the tomcat 6 in the Fedora and >>> Centos. Usually i use shell file to shutdown. After shutting down when >> see >>> the postgre preocess by [code]*ps -ef | grep java*[/code] it is still >> showing >>> the process as running. >>> >>> such as >>> >>> [code] tomcat 14694 1 72 Apr23 ? 23:44:25 >>> /usr/java/jdk1.5.0_13/jre/bin/java >>> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager >>> >> -Djava.util.logging.config.file=/usr/share/tomcat6/apache-tomcat-6.0.18/conf/logging.properties >>> -verbose:gc -Xloggc:gc.log -XX:+PrintGCDetails -XX:MaxPermSize=512M >>> -Xms1024M -Xmx1024M -Djava.awt.headless=true >>> -Djava.endorsed.dirs=/usr/share/tomcat6/apache-tomcat-6.0.18/endorsed >>> -classpath :/usr/share/tomcat6/apache-tomcat-6.0.18/bin/bootstrap.jar >>> >>> -Dcatalina.base=/usr/share/tomcat6/apache-tomcat-6.0.18 >>> -Dcatalina.home=/usr/share/tomcat6/apache-tomcat-6.0.18 >>> -Djava.io.tmpdir=/usr/share/tomcat6/apache-tomcat-6.0.18/temp >>> org.apache.catalina.startup.Bootstrap start [/code] >>> >>> So if i keep repeating the start and shutdown after few cycles it is >>> completely refusing to start. What might be the source or reason of this >>> problem? Advance Thanks, >> If you are leaving an active process behind when you stop the server, >> then doing it lots of times over isn't going to be healthy. >> >> Usually this is because your application has left non-daemon threads >> running that haven't been shutdown. It was was recently pointed out (on >> this list) that the Quartz job scheduler is often a culprit in this regard. >> >> If you have are starting threads yourself, then you need to make sure >> that you properly terminate them when the application (and server) shuts >> down. >> >> A ServletContextListener is useful in this regard. >> >> >> p >> >> >>> Arvind S >>> >>> >>> >>> * >>> "Many of lifes failure are people who did not realize how close they were >> to >>> success when they gave up." >>> -Thomas Edison* >>> >> >> --------------------------------------------------------------------- >> 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
