[
https://issues.apache.org/jira/browse/ACCUMULO-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated ACCUMULO-1709:
-------------------------------------
Attachment: ACCUMULO-1709-001.patch
Patch that
# has master call system.exit on an exception
# makes sure all failure paths through {{start.main()}} exit
# changed exception reporting in {{start.main()}} to invoke
{{Throwable.toString()}} rather than {{Throwable.getMessage()}}. Some
exceptions including {{NullPointerException}} have a null message -calling
{{toString()}} is the only way to reliably get details on all exceptions
> failing Master doesn't set exit code of process
> -----------------------------------------------
>
> Key: ACCUMULO-1709
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1709
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Steve Loughran
> Attachments: ACCUMULO-1709-001.patch
>
>
> If the master can't start up due to an exception, it logs it, but doesn't
> exit the process with any error code -so the failure isn't picked up by any
> scripts looking at the exit code of bin/accumulo
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira