Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-1323

Log extension module loading errors other than ModuleNotFoundException at ERROR

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 8.0.0.Alpha1
    • None
    • Management
    • None

      ExtensionAddHandler is converting all ModuleLoadExceptions to OFE, which means they only get logged at DEBUG post-boot.

      This can be more precise – a ModuleNotFoundException is likely a user error (wrong module name) and thus should get the current treatment. But other ModuleLoadExceptions likely indicate some issue with the server installation and deserve ERROR level logging. Solution is to wrap those in a RuntimeException instead of an OFE.

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

              Created:
              Updated:
              Resolved: