[
https://issues.jboss.org/browse/AS7-6128?page=com.atlassian.jira.plugin.s...
]
Michael Harvey commented on AS7-6128:
-------------------------------------
Jim, Can you elaborate more precisely on steps? "I was doing the CLI activities per
the guide on a domain instance. I fat fingered a bunch of things, and was getting
errors."
Were you able to recover any logs with error messages directly after the server
non-responding incident/potential race condition and prior to the restart?
This is going to be very hard to get to the bottom of and debug given the limited nature
of the report.
In domain mode after some CLI I was not able to restart a particular
host until..
---------------------------------------------------------------------------------
Key: AS7-6128
URL:
https://issues.jboss.org/browse/AS7-6128
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Environment: Linux and EAP 6
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
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