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

Imprecise messages related to slave HC being unable to connect to master

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 3.0.0.Alpha10
    • None
    • Management
    • None

      If a slave fails to connect to the master it logs "Could not connect to master. Aborting. Error was: %s" but since WFCORE-316 it no longer always aborts.

      Plus when it does abort it uses the deprecated SystemExiter.exit method.

      So we should change the first message to drop the bit about aborting and then if we do really abort pass an abort message to SystemExiter.

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: