-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten,
On 6/17/2009 2:04 PM, CBy wrote:
> Thank you, Christopher. It appears that I now have to ways to solve my
> problem. Calling shutdown() stops the threads orderly, so I think I'll
> opt for the ContextListener, although I am not 100% sure.
I'
Thank you, Christopher. It appears that I now have to ways to solve my
problem. Calling shutdown() stops the threads orderly, so I think I'll
opt for the ContextListener, although I am not 100% sure.
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten,
On 6/17/20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten,
On 6/17/2009 4:33 AM, CBy wrote:
> O'Reilly's Tomcat The Definitive Guide advises me to invoke the
> setDaemon(true) method on any Thread object a web application creates to
> keep them from hanging the JVM when Tomcat shuts down. My web serv
CBy wrote:
Thanks for pointing me in the right direction André. A
ServletContextListener fixed my problem.
My own contribution was minimal, and due mainly to the fact that I am
eavesdropping on the real Tomcat experts conversations here and
remembering some things, even if I never used them m
Thanks for pointing me in the right direction André. A
ServletContextListener fixed my problem.
André Warnier wrote:
CBy wrote:
O'Reilly's Tomcat The Definitive Guide advises me to invoke the
setDaemon(true) method on any Thread object a web application creates
to keep them from hanging the
CBy wrote:
O'Reilly's Tomcat The Definitive Guide advises me to invoke the
setDaemon(true) method on any Thread object a web application creates to
keep them from hanging the JVM when Tomcat shuts down. My web service,
however, uses a thread pool that is created via
java.util.concurrent.Execut
S Arvind wrote:
> 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..
Good news. And now you know 2 things: how to diagno
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 we
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 ", and
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 ...
-Arvind S
*
"Many of lifes failure are people who did n
> Did you write your application?
>>> there are team of 200 Engineers wrote that application so i dont know
> where the problem is
One (or more) of them made a mistake, and has left a non-daemon thread
running.
You need to find out what thread is running. One way to do this is to
get a thread du
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
> --A
Is the application completely unchanged for deployment on Tomcat 6?
>> yes it is completely *unchanged*... is anything must be changed for
quartz?
--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
ulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> From: arvindw...@gmail.com
> Date: Sat, 25 Apr 2009 14:07:25 +0530
> Subject: Re: tomcat shutdown problem
> To: users@tomcat.apache.org; p...@pidster.com
>
> Thanks pid...
>
> Can u
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 yo
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
Are you starting
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 multip
Thanks pid...
Can u able to give me more idea to solve it if possible..
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 wrote:
> S Arvind wrote:
> > A wierd proble
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
19 matches
Mail list logo
