Uploaded image for project: 'Thorntail'
  1. Thorntail
  2. THORN-129

Throw container StartExceptions instead of logging them and moving on

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.0.0.Alpha6
    • Component/s: None
    • Labels:
      None

      Description

      This change makes it so that any exceptions that come from WildFly
      during container start get thrown by RuntimeServer#start instead of
      just being logged by WildFly. This is especially useful in testing
      scenarios where tests do container.start().stop() since that kind of
      test can't otherwise detect various kinds of errors upon startup.

      We may want this to just be enabled with some special testing flag, or
      maybe we'd always like to throw the exception on start since Swarm is
      used in more embedded scenarios. It's up for debate, so discuss before
      merging.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                bbrowning Bruce Browning
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: