[
https://issues.jboss.org/browse/WFCORE-1611?page=com.atlassian.jira.plugi...
]
Chao Wang moved JBEAP-5100 to WFCORE-1611:
------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1611 (was: JBEAP-5100)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
Target Release: (was: 7.backlog.GA)
Affects Version/s: 3.0.0.Alpha2
(was: 7.0.0.GA)
CLI could stuck if SIGINT is send during authentication dialogue
----------------------------------------------------------------
Key: WFCORE-1611
URL:
https://issues.jboss.org/browse/WFCORE-1611
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 3.0.0.Alpha2
Reporter: Chao Wang
Assignee: Chao Wang
Interruption a CLI session with Ctrl+C during authentication dialogue could get CLI into
unresponsive state.
*reproduce*
Either use a remote server, --no-local-auth cli script arg or remove a local element from
ManagementRealm configuration
{code:diff}
<security-realms>
<security-realm name="ManagementRealm">
<authentication>
- <local default-user="$local"
skip-group-loading="true"/>
{code}
start a standalone server and launch a CLI
{noformat}
[pkremens@localhost] $ ./standalone.sh &
[pkremens@localhost] $ ./jboss-cli.sh
[disconnected /] connect
Authenticating against security realm: ManagementRealm
Username: <Press Ctrl+C here>
{noformat}
Could not connect message is printed, but process is not terminated and stuck at this
point.
{noformat}
The controller is not available at localhost:9990: java.net.ConnectException:
WFLYPRT0023: Could not connect to http-remoting://localhost:9990. The connection timed
out: WFLYPRT0023: Could not connect to http-remoting://localhost:9990. The connection
timed out
{noformat}
Only way to recover the terminal is to SIGKILL the CLI process.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)