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

Editing of default deployment scanner's relative-to attribute can cause server crash

    XMLWordPrintable

Details

    • Hide
      1. Start server in standalone mode
      2. Change value of relative-to attribute to non-existing value. /subsystem=deployment-scanner/scanner=default:write-attribute(name=relative-to, value=foobar)
      3. :reload
      4. Server is down and have to be started with corrected configuration. Cannot be fixed using CLI.
      Show
      Start server in standalone mode Change value of relative-to attribute to non-existing value. /subsystem=deployment-scanner/scanner=default:write-attribute(name=relative-to, value=foobar) :reload Server is down and have to be started with corrected configuration. Cannot be fixed using CLI.

    Description

      Setting value of relative-to attribute of default deployment scanner on standalone server to a path which does not exists in file system causes server crash.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3044 Editing of default deployment scanner's relative-to attribute can cause server crash

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-4874 Perform check when changing 'path' attribute of 'deployment-scanner' instance

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-1579 Perform check when changing 'path' attribute of 'deployment-scanner' instance

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

              chaowan@redhat.com Chao Wang
              chaowan@redhat.com Chao Wang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: