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

Unhelpful error message when OSH throws an exception with no detail message

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.0.0.Alpha4
    • 1.0.0.Alpha3
    • Management
    • None

      This shows up a fair amount in issue reports, either in the CLI output or in the server log:

      "failure-description" => "JBAS014749: Operation handler failed: null"

      The null happens because the message is getting passed the result of throwable.getLocalizedMessage() and that may be null. See DMR-11 for what's likely the most common reason it's null.

      If it's null, the code should use the class name of the error message.

              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: