[jboss-jira] [JBoss JIRA] (WFCORE-1780) Imprecise messages related to slave HC being unable to connect to master

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFCORE-1780:
-------------------------------------
    Description: 
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.

  was:
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 abort aborting and then if we do really abort pass an abort message to SystemExiter.



> Imprecise messages related to slave HC being unable to connect to master
> ------------------------------------------------------------------------
>
>                 Key: WFCORE-1780
>                 URL: https://issues.jboss.org/browse/WFCORE-1780
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>            Priority: Minor
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)