Hi,
I'm still investigating this issue. Same behaviour if I use manager
directly through the interface instead of using ant task.
There has been a message reciently explaining the causes of
undeployement problem. It says that an application not shutting down
properly because threads still running. Below you can see the thread
dump of my webapp only stopped and not deployed. To me, it seems like
everything is ok, and threads are not waiting for my webapp.
Any hints on this issue? To me it seems like something has changed
in tomcat 6.0.16 because undeployement works ok until this version.
Many Thanks
Full thread dump Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode):
"http-8080-2" daemon prio=6 tid=0x0ae56dc8 nid=0x858 in Object.wait()
[0x0b70f000..0x0b70f9e8]
at java.lang.Object.wait(Native Method)
- waiting on <0x0339e828> (a
org.apache.tomcat.util.net.JIoEndpoint$Worker)
at java.lang.Object.wait(Object.java:474)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.await(JIoEndpoint.java:416)
- locked <0x0339e828> (a
org.apache.tomcat.util.net.JIoEndpoint$Worker)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:442)
at java.lang.Thread.run(Thread.java:595)
"http-8080-1" daemon prio=6 tid=0x0ae6bfb0 nid=0xb34 in Object.wait()
[0x0b6cf000..0x0b6cfa68]
at java.lang.Object.wait(Native Method)
- waiting on <0x0335bd28> (a
org.apache.tomcat.util.net.JIoEndpoint$Worker)
at java.lang.Object.wait(Object.java:474)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.await(JIoEndpoint.java:416)
- locked <0x0335bd28> (a
org.apache.tomcat.util.net.JIoEndpoint$Worker)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:442)
at java.lang.Thread.run(Thread.java:595)
"TP-Monitor" daemon prio=6 tid=0x0ae6b1d8 nid=0xa44 in Object.wait()
[0x0b68f000..0x0b68fae8]
at java.lang.Object.wait(Native Method)
- waiting on <0x0334cd30> (a
org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable)
at
org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPool.java:565)
- locked <0x0334cd30> (a
org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable)
at java.lang.Thread.run(Thread.java:595)
"TP-Processor4" daemon prio=6 tid=0x0ad5bb88 nid=0x720 runnable
[0x0b64f000..0x0b64fbe8]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked <0x0334cdd8> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at org.apache.jk.common.ChannelSocket.accept(ChannelSocket.java:306)
at
org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java:660)
at
org.apache.jk.common.ChannelSocket$SocketAcceptor.runIt(ChannelSocket.java:870)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
at java.lang.Thread.run(Thread.java:595)
"TP-Processor3" daemon prio=6 tid=0x0ad5ba00 nid=0x83c in Object.wait()
[0x0b60f000..0x0b60fb68]
at java.lang.Object.wait(Native Method)
- waiting on <0x0334cfe8> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:474)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:662)
- locked <0x0334cfe8> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Thread.run(Thread.java:595)
"TP-Processor2" daemon prio=6 tid=0x0ad5c478 nid=0x468 in Object.wait()
[0x0b5cf000..0x0b5cfc68]
at java.lang.Object.wait(Native Method)
- waiting on <0x0334d080> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:474)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:662)
- locked <0x0334d080> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Thread.run(Thread.java:595)
"TP-Processor1" daemon prio=6 tid=0x0ad5c260 nid=0x6a8 in Object.wait()
[0x0b58f000..0x0b58fce8]
at java.lang.Object.wait(Native Method)
- waiting on <0x0334d118> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:474)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:662)
- locked <0x0334d118> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Thread.run(Thread.java:595)
"http-8080-Acceptor-0" daemon prio=6 tid=0x0b055da8 nid=0xa40 runnable
[0x0b54f000..0x0b54fd68]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked <0x02feb840> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at
org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:61)
at
org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:310)
at java.lang.Thread.run(Thread.java:595)
"ContainerBackgroundProcessor[StandardEngine[Catalina]]" daemon prio=6
tid=0x0af2ff80 nid=0xf3c waiting on condition [0x0b50f000..0x0b50f9e8]
at java.lang.Thread.sleep(Native Method)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1579)
at java.lang.Thread.run(Thread.java:595)
"Low Memory Detector" daemon prio=6 tid=0x0096dbf8 nid=0x264 runnable
[0x00000000..0x00000000]
"CompilerThread0" daemon prio=10 tid=0x0096c888 nid=0xa78 waiting on
condition [0x00000000..0x0abff848]
"Signal Dispatcher" daemon prio=10 tid=0x0096bc08 nid=0xd38 waiting on
condition [0x00000000..0x00000000]
"Finalizer" daemon prio=8 tid=0x00962c28 nid=0xb58 in Object.wait()
[0x0ab7f000..0x0ab7fc68]
at java.lang.Object.wait(Native Method)
- waiting on <0x02f1bfb0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x02f1bfb0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x009617b8 nid=0x578 in
Object.wait() [0x0ab3f000..0x0ab3fce8]
at java.lang.Object.wait(Native Method)
- waiting on <0x02f1c030> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0x02f1c030> (a java.lang.ref.Reference$Lock)
"main" prio=6 tid=0x000377a8 nid=0x8c8 runnable [0x0007f000..0x0007fc3c]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked <0x0335bef0> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at
org.apache.catalina.core.StandardServer.await(StandardServer.java:389)
at org.apache.catalina.startup.Catalina.await(Catalina.java:642)
at org.apache.catalina.startup.Catalina.start(Catalina.java:602)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
"VM Thread" prio=10 tid=0x0095ed08 nid=0xcec runnable
"VM Periodic Task Thread" prio=10 tid=0x0096ef80 nid=0xd70 waiting on
condition
Diego Rodríguez Martín escribió:
Hi,
I'm using manager in Tomcat 6.0.16 throught ant task (1.6.5) to
undeploy webapps. I have copied the new catalina-ant.jar in
ANT_HOME/lib directory.
The problem is that now the application is stopped instead of
undeployed though the output message is "undeployed app at context
/xxxxxx". I then use list task and my webapp is in status stopped. If
I execute again the undeploy task, the output message is again
"undeployed app at context /xxxxxx" but this time the webapp is
undeployed and not listed anymore. It seems like the task is
undeploying in two steps. I have been using the undeploy task since
4.1.27 version and the task never behaved that way. I have search the
docs and there is no info about any change in 6.0.16 (6.0.14 is ok)
Are there any undocumented changes in 6.0.16 or is it a malfunction?
--
-------------------------------------------------------------
Diego Rodríguez Martín ([EMAIL PROTECTED])
ALTIRIA TIC - Servicios SMS - Desarrollo Web
Tel. +34 913311198 - Fax +34 915713993 - Móvil +34 610299750
www.altiria.com
-------------------------------------------------------------
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
