Yuliya Feldman created TWILL-243:
------------------------------------

             Summary: Failed BundleRunnable is stuck in exiting state
                 Key: TWILL-243
                 URL: https://issues.apache.org/jira/browse/TWILL-243
             Project: Apache Twill
          Issue Type: Bug
          Components: ext, yarn
            Reporter: Yuliya Feldman


I am using BundleRunnable and so far my experience was that in case of failure 
of my runnable container process never exits.

And my impression it pretty much all the time stuck in executing Shutdown hooks 
(not even my application specific)

Here is ThreadDump for that thread:

"TwillContainerService" #32 prio=5 os_prio=0 tid=0x00007f1590297800 nid=0x4de2 
in Object.wait() [0x00007f15805d9000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        at java.lang.Thread.join(Thread.java:1249)
        - locked <0x00000000ff9c41d0> (a 
org.apache.twill.internal.ServiceMain$1)
        at java.lang.Thread.join(Thread.java:1323)
        at 
java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:106)
        at 
java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)
        at java.lang.Shutdown.runHooks(Shutdown.java:123)
        at java.lang.Shutdown.sequence(Shutdown.java:167)
        at java.lang.Shutdown.exit(Shutdown.java:212)
        - locked <0x00000000ff6363e8> (a java.lang.Class for java.lang.Shutdown)
        at java.lang.Runtime.exit(Runtime.java:109)
        at java.lang.System.exit(System.java:971)
        at 
org.apache.twill.ext.BundledJarRunnable.run(BundledJarRunnable.java:59)
        at 
org.apache.twill.internal.container.TwillContainerService.doRun(TwillContainerService.java:130)
        at 
org.apache.twill.internal.AbstractTwillService.run(AbstractTwillService.java:181)
        at 
twill.com.google.common.util.concurrent.AbstractExecutionThreadService$1$1.run(AbstractExecutionThreadService.java:52)
        at java.lang.Thread.run(Thread.java:745)

Just wonder if anybody else experienced similar.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to