[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)]

     [ https://issues.jboss.org/browse/WFLY-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Kumar SenSharma updated WFLY-3970:
--------------------------------------
    Description: 
- 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*

  was:
- 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**



> 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)