Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-4954

CLI could stuck if SIGINT is send during authentication dialogue

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.DR2
    • 7.0.0.GA
    • CLI
    • None

      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

      Unable to find source-code formatter for language: diff. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
               <security-realms>
                   <security-realm name="ManagementRealm">
                       <authentication>
      -                    <local default-user="$local" skip-group-loading="true"/>
      

      start a standalone server and launch a CLI

      [pkremens@localhost] $ ./standalone.sh &
      [pkremens@localhost] $ ./jboss-cli.sh
      [disconnected /] connect
      Authenticating against security realm: ManagementRealm
      Username: <Press Ctrl+C here>
      

      Could not connect message is printed, but process is not terminated and stuck at this point.

      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
      

      Only way to recover the terminal is to SIGKILL the CLI process.

            chaowan@redhat.com Chao Wang
            pkremens@redhat.com Petr Kremensky (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: