Pid thanks very much. We found the thread from the thread dump. Problem we did is we didnt shutdown the quartz scheduler. Now as per ur guidelines in the context listener we did that. It currently in testing phase. Thanks..
"Many of lifes failure are people who did not realize how close they were to success when they gave up." -Thomas Edison On Mon, Apr 27, 2009 at 7:50 PM, Pid <p...@pidster.com> wrote: > S Arvind wrote: > > Pid very thanks for guiding me .. one more help alone... can u please > tell > > me how to check which thread it is runnin by quartz other then checking > code > > ... i am centos, jvm 5, tomcat 5 and tomcat 6.. i think i am disturbin u > > lot, but ... > > As Dan said, "kill -QUIT <pid>", and as I said previously, familiarise > yourself with jstack, jmap and possibly jconsole, all of which are > command line tools available with the Sun JREs. > > 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* > > > > > > On Mon, Apr 27, 2009 at 7:18 PM, Pid <p...@pidster.com> wrote: > > > >> S Arvind wrote: > >>> Is the application completely unchanged for deployment on Tomcat 6? > >>>>> yes it is completely *unchanged*... is anything must be changed for > >>> quartz? > >> okay, then your best bet is to explore what the JVM is doing after > >> shutdown and check which threads are still running. > >> > >> 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 > >>> * > >>> > >>> On Sat, Apr 25, 2009 at 5:06 PM, Pid <p...@pidster.com> wrote: > >>> > >>>> Please do not keep using "reply to all". It is annoying and > >>>> unnecessary. I will obviously receive a copy of the mail if you just > >>>> send a reply to the list. > >>>> > >>>>> Did you write your application? > >>>>>>> there are team of 200 Engineers wrote that application so i dont > know > >>>>> where the problem is > >>>>> Are you using Quartz in your application? > >>>>>>> yeah we have quartz scheduler in our application. But when we run > in > >>>>> Tomcat 5 we dont have this kind of problem > >>>> Is the application completely unchanged for deployment on Tomcat 6? > >>>> > >>>> When you shutdown, Quartz will log a message describing the number of > >>>> running threads, this may help diagnose the problem. The count may be > >>>> above 20, but that isn't necessarily a bad thing. > >>>> > >>>> > >>>>> Are you starting new Threads in your app? > >>>>>>> Might be, i have to ask each team. > >>>> Check that they are being properly terminated. Even if the devs > promise > >>>> they are, double check. > >>>> > >>>>> When you have started and stopped the application a few times are > there > >>>>> still multiple java processes running? > >>>>>>> YES, this is the only thing assigned to me to correct it. > >>>> You should ensure that the old processes are terminated before > starting > >>>> new ones, as an old one may hang onto one of the ports that Tomcat > uses, > >>>> thus preventing new instances from starting up. > >>>> > >>>> The Linux "kill" command can do this. > >>>> > >>>> > >>>> However... > >>>> > >>>> After shutdown has been requested and while the process is still > >>>> running, take a thread dump, or use the java tools to examine the > state > >>>> of the JVM. See if you can spot which Threads are still running. > >>>> > >>>> Try jmap, jstack and jconsole (if you're on a local machine). > >>>> > >>>> > >>>> p > >>>> > >>>> > >>>> > >>>> > >>>>> *"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:21 PM, Pid <p...@pidster.com> wrote: > >>>>> > >>>>>> 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 > >>>>>> > >>>>>> > >>>> --------------------------------------------------------------------- > >>>> 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 > >> > >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
