Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-2250

CLI can exit although Aesh console has not been cleaned

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 3.0.0.Alpha23
    • None
    • CLI
    • None

      2 Threads. Thread1 is polling Aesh console status for its running state, as soon as the state is switched to !running, the CLI exists.
      Ctrl-C is sent to CLI, Aesh command Thread initiates a shutdown, the CLI calls console.stop(). Aesh change running state to be false THEN does some cleanup. If thread1 is scheduled, then CLI exists although cleanup has not yet been operated. leaving an insane TTY.

      The fix is to switch to Aesh 0.66.15 in which this bug has been fixed.

              jdenise@redhat.com Jean Francois Denise
              jdenise@redhat.com Jean Francois Denise
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: