Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-162

Host controller hangs and can not be stopped if Managed Server is killed after establishing MBean connection.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.0.0.Alpha10
    • 1.0.0.Alpha9
    • Management
    • None
    • Hide

      Mentioned in issue description.

      Show
      Mentioned in issue description.
    • Workaround Exists
    • Hide

      kill the host controller using "kill -9 $PID"

      Show
      kill the host controller using "kill -9 $PID"

    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

      Attachments

        Activity

          People

            emuckenhuber_jira Emanuel Muckenhuber (Inactive)
            jaysensharma Jay SenSharma (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: