[jboss-jira] [JBoss JIRA] (WFLY-1170) In domain mode after some CLI I was not able to restart a particular host until..

[Emanuel Muckenhuber (JIRA)]

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

Emanuel Muckenhuber resolved WFLY-1170.
---------------------------------------

         Assignee: Emanuel Muckenhuber  (was: Brian Stansberry)
    Fix Version/s: 8.0.0.CR1
       Resolution: Out of Date


I am resolving this as out of date, since there was no activity and we fixed a few issues related to hangs in the domain over the last time.
                
> In domain mode after some CLI I was not able to restart a particular host until..
> ---------------------------------------------------------------------------------
>
>                 Key: WFLY-1170
>                 URL: https://issues.jboss.org/browse/WFLY-1170
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>         Environment: Linux and EAP 6
>            Reporter: Jim Tyrrell
>            Assignee: Emanuel Muckenhuber
>             Fix For: 8.0.0.CR1
>
>
> Running the examples in the JB348 Admin II class around the CLI section I uncovered an odd error, that I was not able to reproduce, and no one else seemed to have, but I thought I should log it here.
> In the class last week I was doing the CLI activities per the guide on a domain instance.  I fat fingered a bunch of things, and was getting errors.  Once I was done making the changes with any errors I tried to restart host1 in the web console.  This errored out without a good error message.  After a few times of that I tried cntrl-cing in the console, only to have the server shutdown after about 5 minutes or so of hitting cntrl-c.  I did not notice any error messages, but it makes me think some sort of racing, or locking condition exists in domain mode. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira