[jboss-jira] [JBoss JIRA] (AS7-1833) CLI usability: operation :shutdown results in "Communication error"
[
https://issues.jboss.org/browse/AS7-1833?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-1833:
----------------------------------------
The communication error is out of date now. But now there is another issue, we don't
have a notion of "connection closed" event and the cli remains in the
"connected" state. And if a user tries to communicate with the controller it
will be hanging for the "time out" amount of time.
So, we need some connection status checking api/notifications to handle this better.
And also take into account :reload and automatic re-connection (if we want to support
that).
CLI usability: operation :shutdown results in "Communication
error"
-------------------------------------------------------------------
Key: AS7-1833
URL: https://issues.jboss.org/browse/AS7-1833
Project: Application Server 7
Issue Type: Enhancement
Components: CLI
Affects Versions: 7.0.0.Final, 7.0.1.Final
Reporter: Radoslav Husar
Assignee: Alexey Loubyansky
Priority: Minor
Labels: eap6-ux
Fix For: 7.1.1.Final
If you shutdown the server, you get an error:
{code}
[standalone@localhost:9999 /] :shutdown
Communication error: Channel closed
Closed connection to localhost:9999
{code}
Even though its considered by this comment clean -
https://issues.jboss.org/browse/AS7-689?focusedCommentId=12614756&pag...
- I is not really clean as you get an error but termination of the channel can be
anticipated. Users might be confused now knowing if its an actual error or not. For
example take a look at SSH.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira