The default answer is to check your webapps for non-daemon threads not properly closed by the webapp. Some webapp has created it's own non-daemon threads without a ServletContextListener to close them down. Let ups know if that's not the case.
--David santosh.si...@birlasoft.com wrote: > Hi > > tomcat 24453 1 2 16:11 pts/4 00:00:23 > /opt/java1.5/jdk1.5.0_10/bin/java > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Djava.endorsed.dirs=/opt/jakarta-tomcat-5.5.9/common/endorsed > -classpath > :/opt/jakarta-tomcat-5.5.9/bin/bootstrap.jar:/opt/jakarta-tomcat-5.5.9/b > in/commons-logging-api.jar -Dcatalina.base=/opt/jakarta-tomcat-5.5.9 > -Dcatalina.home=/opt/jakarta-tomcat-5.5.9 > -Djava.io.tmpdir=/opt/jakarta-tomcat-5.5.9/temp > org.apache.catalina.startup.Bootstrap start > > > tomcat 24454 1 0 16:11 pts/4 00:00:00 /usr/local/sbin/cronolog > /opt/jakarta-tomcat-5.5.9/logs/catalina.out.%Y-%m-%d > > > Above 2 processes are not closing from operating system level even after > shutting down the tomcat. > > Operating System --- RHEL 4 > > Default web server with OS --- jakarta-tomcat-5.5.9 > > Default Java --- JAVA 1.5 > > Database --- Oracle 10.2.0.4.0 > > Regards > > Santosh > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
