[jboss-jira] [JBoss JIRA] (WFLY-3970) Host controller hangs and can not be stopped if Managed Server is killed after establishing MBean connection.

Jay Kumar SenSharma (JIRA) issues at jboss.org
Mon Oct 13 05:48:35 EDT 2014 

    [ https://issues.jboss.org/browse/WFLY-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011043#comment-13011043 ] 

Jay Kumar SenSharma edited comment on WFLY-3970 at 10/13/14 5:48 AM:
---------------------------------------------------------------------

Some of the BLOCKED Threads on Host Controller can be seen as following:

{code}
"main" prio=10 tid=0x00007fe60c009800 nid=0x34d0 waiting for monitor entry [0x00007fe613c51000]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at java.lang.Shutdown.exit(Shutdown.java:212)
	- waiting to lock <0x00000000e0897418> (a java.lang.Class for java.lang.Shutdown)
	at java.lang.Runtime.exit(Runtime.java:109)
	at java.lang.System.exit(System.java:962)
	at org.jboss.as.host.controller.SystemExiter$DefaultExiter.exit(SystemExiter.java:54)
	at org.jboss.as.host.controller.SystemExiter.exit(SystemExiter.java:41)
	at org.jboss.as.host.controller.Main.exit(Main.java:172)
	at org.jboss.as.host.controller.Main.main(Main.java:115)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.modules.Module.run(Module.java:312)
	at org.jboss.modules.Main.main(Main.java:460)


"SIGINT handler" daemon prio=10 tid=0x00007fe5e800e800 nid=0x3709 waiting for monitor entry [0x00007fe601d8f000]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at java.lang.Shutdown.exit(Shutdown.java:212)
	- waiting to lock <0x00000000e0897418> (a java.lang.Class for java.lang.Shutdown)
	at java.lang.Terminator$1.handle(Terminator.java:52)
	at sun.misc.Signal$1.run(Signal.java:212)
	at java.lang.Thread.run(Thread.java:744)

"SIGINT handler" daemon prio=10 tid=0x00007fe5e8004000 nid=0x36b2 in Object.wait() [0x00007fe60106a000]
   java.lang.Thread.State: WAITING (on object monitor)
	at java.lang.Object.wait(Native Method)
	- waiting on <0x00000000e08971b8> (a org.jboss.as.host.controller.HostControllerBootstrap$ShutdownHook)
	at java.lang.Thread.join(Thread.java:1280)
	- locked <0x00000000e08971b8> (a org.jboss.as.host.controller.HostControllerBootstrap$ShutdownHook)
	at java.lang.Thread.join(Thread.java:1354)
	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 <0x00000000e0897418> (a java.lang.Class for java.lang.Shutdown)
	at java.lang.Terminator$1.handle(Terminator.java:52)
	at sun.misc.Signal$1.run(Signal.java:212)
	at java.lang.Thread.run(Thread.java:744)
{code}


was (Author: jaysensharma):
Some of the BLOCKED Threads can be seen as following:

{code}
"main" prio=10 tid=0x00007fe60c009800 nid=0x34d0 waiting for monitor entry [0x00007fe613c51000]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at java.lang.Shutdown.exit(Shutdown.java:212)
	- waiting to lock <0x00000000e0897418> (a java.lang.Class for java.lang.Shutdown)
	at java.lang.Runtime.exit(Runtime.java:109)
	at java.lang.System.exit(System.java:962)
	at org.jboss.as.host.controller.SystemExiter$DefaultExiter.exit(SystemExiter.java:54)
	at org.jboss.as.host.controller.SystemExiter.exit(SystemExiter.java:41)
	at org.jboss.as.host.controller.Main.exit(Main.java:172)
	at org.jboss.as.host.controller.Main.main(Main.java:115)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.modules.Module.run(Module.java:312)
	at org.jboss.modules.Main.main(Main.java:460)


"SIGINT handler" daemon prio=10 tid=0x00007fe5e800e800 nid=0x3709 waiting for monitor entry [0x00007fe601d8f000]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at java.lang.Shutdown.exit(Shutdown.java:212)
	- waiting to lock <0x00000000e0897418> (a java.lang.Class for java.lang.Shutdown)
	at java.lang.Terminator$1.handle(Terminator.java:52)
	at sun.misc.Signal$1.run(Signal.java:212)
	at java.lang.Thread.run(Thread.java:744)

"SIGINT handler" daemon prio=10 tid=0x00007fe5e8004000 nid=0x36b2 in Object.wait() [0x00007fe60106a000]
   java.lang.Thread.State: WAITING (on object monitor)
	at java.lang.Object.wait(Native Method)
	- waiting on <0x00000000e08971b8> (a org.jboss.as.host.controller.HostControllerBootstrap$ShutdownHook)
	at java.lang.Thread.join(Thread.java:1280)
	- locked <0x00000000e08971b8> (a org.jboss.as.host.controller.HostControllerBootstrap$ShutdownHook)
	at java.lang.Thread.join(Thread.java:1354)
	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 <0x00000000e0897418> (a java.lang.Class for java.lang.Shutdown)
	at java.lang.Terminator$1.handle(Terminator.java:52)
	at sun.misc.Signal$1.run(Signal.java:212)
	at java.lang.Thread.run(Thread.java:744)
{code}

> Host controller hangs and can not be stopped if Managed Server is killed after establishing MBean connection.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-3970
>                 URL: https://issues.jboss.org/browse/WFLY-3970
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 9.0.0.Alpha1
>         Environment: Linux
>            Reporter: Jay Kumar SenSharma
>            Assignee: Brian Stansberry
>         Attachments: Host_Controller_ThreadDumps.txt
>
>
> - If the following sequence of events hapens then the Host controller process hangs and it can not be stopped using "CTRL+C" command. (only kill -9 works)
> **Step-1).** Start the default "wildfly-9.0.0.Alpha1" in domain mode using "./domain.sh" script.  (it should start server-one, server-two, Host controller and process controller)
> **Step-2).** Open the JConsole using "wildfly-9.0.0.Alpha1/bin/jconsole.sh" script. 
> **Step-3).** In JConsole connect to "server-one" and then nevigate to "MBeans" tab just to check if the MBeans are  visible in jconsole or not.
> **Step-4).** Now kill the "server-one" process using "kill  -9  $PID" command
> **Step-5).** Once server-one is killed try stopping the Host Controller process  using "CTRL+C". Press CTRL+C in the terminal where the "./domain.sh" script is being executed. 
> Users will notice that the CTRL+C signal is also not able to kill the host controller process. 
> **Thread Dumps Atached**



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

More information about the jboss-jira mailing list