[
https://issues.jboss.org/browse/AS7-1833?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on AS7-1833:
----------------------------------------------
pkremens(a)redhat.com made a comment on [bug
908955|https://bugzilla.redhat.com/show_bug.cgi?id=908955]
Calling new reload command in quick succession I get:
[standalone@localhost:9999 /] reload
[standalone@localhost:9999 /] reload
Failed to execute :reload: java.net.ConnectException: JBAS012144: Could not connect to
remote://localhost:9999. The connection timed out: JBAS012144: Could not connect to
remote://localhost:9999. The connection timed out
[disconnected /]
I tried to to add --timeout argument to CLI calling, but ConnectionException occurs
again.
CLI usability: operations that shutdown the server-side management
interface result 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: Critical
Labels: eap6-ux
Fix For: EAP 6.1.0.Alpha (7.2.0.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.
The same basic issue exists for the :reload operation.
--
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