You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Antonio Gallardo <ag...@agsoftware.dnsalias.com> on 2003/03/14 12:09:16 UTC
What is this?
Hi:
I currently downloaded the lastest CVS from cocoon-2.1. I am using Tomcat
4.1.18. After a sucessfull compile of the sources. I noted the following:
1-If I install the cocoon.war into Tomcat, after this I shutdown it using
./shutdown.sh
Please note that I already can see the working examples. The problem is
just at the shutdown. The catalina.out said:
"Stopping service Tomcat-Standalone"
This is the lastest notice and the process remains in memory. Please note:
1- If I uninstall cocoon.war and delete the cocoon directory, tomcat
starts and end correctly (destroy the process).
Also if I used an old cocoon.war from 14-Jan-2003 it works fine!
My environment is:
Red Hat Linux 8.0 lastest patches.
Sun Java SDK 1.4.1_01
Best Regards,
Antonio Gallardo.
Re: Cocoon webapp does not exit cleanly
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Hi!
Thanks fo the tip. I hope it would help to figure where is the problem of
not shutting down properly. Here I put the messages in catalina.out.
I run ./shutdown.sh
and after a kill -QUIT <java_pid>
I am using Tomcat 4.1.18, Sun Java 1.4.1_01 on Red Hat Linux 8.0
Antonio Gallardo
<snip of catalina.out>
Stopping service Tomcat-Standalone
Sun Mar 16 18:56:43 CST 2003 SHUTDOWN : System.exit() was not called
Full thread dump Java HotSpot(TM) Client VM (1.4.1_01-b01 mixed mode):
"DestroyJavaVM" prio=1 tid=0x0x89d3d58 nid=0x55be waiting on condition
[0..bfffc090]
"Thread-16" daemon prio=1 tid=0x0x82443b8 nid=0x55e4 in Object.wait()
[5b409000..5b409830]
at java.lang.Object.wait(Native Method)
- waiting on <0x4d09cee0> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:426)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:509)
- locked <0x4d09cee0> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Thread.run(Thread.java:536)
"Thread-11" daemon prio=1 tid=0x0x8240988 nid=0x55df in Object.wait()
[5b184000..5b184830]
at java.lang.Object.wait(Native Method)
- waiting on <0x4d04fc10> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:426)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:509)
- locked <0x4d04fc10> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Thread.run(Thread.java:536)
"Thread-2" prio=1 tid=0x0x8a14598 nid=0x55d2 in Object.wait()
[5c2d0000..5c2d0830]
at java.lang.Object.wait(Native Method)
- waiting on <0x4c420070> (a EDU.oswego.cs.dl.util.concurrent.LinkedNode)
at java.lang.Object.wait(Object.java:426)
at
EDU.oswego.cs.dl.util.concurrent.SynchronousChannel.put(SynchronousChannel.java:152)
- locked <0x4c420070> (a EDU.oswego.cs.dl.util.concurrent.LinkedNode)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$WaitWhenBlocked.blockedAction(PooledExecutor.java:778)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor.execute(PooledExecutor.java:877)
at
org.apache.excalibur.event.command.AbstractThreadManager.run(AbstractThreadManager.java:252)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:727)
at java.lang.Thread.run(Thread.java:536)
"Signal Dispatcher" daemon prio=1 tid=0x0x80b26c8 nid=0x55c5 waiting on
condition [0..0]
"Finalizer" daemon prio=1 tid=0x0x8094618 nid=0x55c2 in Object.wait()
[586a5000..586a5830]
at java.lang.Object.wait(Native Method)
- waiting on <0x4c5fe5d0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
- locked <0x4c5fe5d0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=1 tid=0x0x8093a68 nid=0x55c1 in
Object.wait() [58624000..58624830]
at java.lang.Object.wait(Native Method)
- waiting on <0x4c5fe638> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:426)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:113)
- locked <0x4c5fe638> (a java.lang.ref.Reference$Lock)
"VM Thread" prio=1 tid=0x0x8090808 nid=0x55c0 runnable
"VM Periodic Task Thread" prio=1 tid=0x0x80b1310 nid=0x55c3 waiting on
condition
"Suspend Checker Thread" prio=1 tid=0x0x80b1c78 nid=0x55c4 runnable
</snip of catalina.out>
Cocoon webapp does not exit cleanly
Posted by Santiago Gala <sg...@hisitech.com>.
Antonio Gallardo wrote:
> Hi:
>
> I currently downloaded the lastest CVS from cocoon-2.1. I am using Tomcat
> 4.1.18. After a sucessfull compile of the sources. I noted the following:
>
> 1-If I install the cocoon.war into Tomcat, after this I shutdown it using
> ./shutdown.sh
>
> Please note that I already can see the working examples. The problem is
> just at the shutdown. The catalina.out said:
>
> "Stopping service Tomcat-Standalone"
>
> This is the lastest notice and the process remains in memory. Please note:
Quite possibly, a thread in Cocoon or your app does not have
"setDaemon(true)".
To find the culprit, "Kill -QUIT <atomcatpid>" and look for it in
catalina.out
>
> 1- If I uninstall cocoon.war and delete the cocoon directory, tomcat
> starts and end correctly (destroy the process).
>
> Also if I used an old cocoon.war from 14-Jan-2003 it works fine!
>
> My environment is:
>
> Red Hat Linux 8.0 lastest patches.
> Sun Java SDK 1.4.1_01
>
> Best Regards,
>
> Antonio Gallardo.
>
Re: What is this?
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Hi Jeff!
Thanks for the answer. I was going crazy with this. Also I was trying the
new 4.1.21 BETA for development purpose when the problrm starts.
This is why I changed all back and trying to resolve this issue. Well, I
looks like I have not Good luck when did the change. :-D
Best Regards,
Antonio Gallardo
Jeff Turner dijo:
> On Fri, Mar 14, 2003 at 05:09:16AM -0600, Antonio Gallardo wrote:
>> Hi:
>>
>> I currently downloaded the lastest CVS from cocoon-2.1. I am using
>> Tomcat 4.1.18. After a sucessfull compile of the sources. I noted the
>> following:
>>
>> 1-If I install the cocoon.war into Tomcat, after this I shutdown it
>> using ./shutdown.sh
>>
>> Please note that I already can see the working examples. The problem
>> is just at the shutdown. The catalina.out said:
>>
>> "Stopping service Tomcat-Standalone"
>>
>> This is the lastest notice and the process remains in memory.
>
> You're right. Yesterday Cocoon shut down fine. Today there's a rogue
> thread preventing a clean exit.
>
> Seems it's all Berin's fault :) At least, locally reverting this patch
> fixes things:
>
> http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/Cocoon.java.diff?r1=1.3&r2=1.4
>
> Looks like this ThreadManager object isn't take through its full
> lifecycle.
>
>
> --Jeff
>
> ...
>> Best Regards,
>>
>> Antonio Gallardo.
>>
>>
Re: What is this?
Posted by Jeff Turner <je...@apache.org>.
On Fri, Mar 14, 2003 at 05:09:16AM -0600, Antonio Gallardo wrote:
> Hi:
>
> I currently downloaded the lastest CVS from cocoon-2.1. I am using Tomcat
> 4.1.18. After a sucessfull compile of the sources. I noted the following:
>
> 1-If I install the cocoon.war into Tomcat, after this I shutdown it using
> ./shutdown.sh
>
> Please note that I already can see the working examples. The problem is
> just at the shutdown. The catalina.out said:
>
> "Stopping service Tomcat-Standalone"
>
> This is the lastest notice and the process remains in memory.
You're right. Yesterday Cocoon shut down fine. Today there's a rogue
thread preventing a clean exit.
Seems it's all Berin's fault :) At least, locally reverting this patch
fixes things:
http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/Cocoon.java.diff?r1=1.3&r2=1.4
Looks like this ThreadManager object isn't take through its full
lifecycle.
--Jeff
...
> Best Regards,
>
> Antonio Gallardo.
>
>