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

Replacing a disabled deployment destroys profile section of xml config

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 10.0.0.Final
    • Fix Version/s: 10.1.0.CR1, 10.1.0.Final
    • Component/s: Server
    • Labels:
      None
    • Environment:

      Fresh install of Wildfly 10 on Ubuntu 15.10 / JDK 8_101

    • Steps to Reproduce:
      Hide

      1. Unpack a fresh WildFly 10.0 Final app server
      2. Modify standalone.xml to bind management and public to <any-address/>. (May not be required in your environment)
      3. bin/add-user.sh and add management user
      4. Start WildFly (bin/standalone.sh)
      5. Log in to management console and add a new deployment. (I tested w/ the wildfly-helloworld.jar from the wildfly/quickstart repo on Github, last commit Jun 20)
      6. If you enabled deployment when creating it, disable it now.
      7. Make note of the size of the standalone.xml configuration file (~20k)
      8. Replace the deployment with the same .jar file
      9. Notice the size of the standalone.xml configuration file (~5k)

      Show
      1. Unpack a fresh WildFly 10.0 Final app server 2. Modify standalone.xml to bind management and public to <any-address/>. (May not be required in your environment) 3. bin/add-user.sh and add management user 4. Start WildFly (bin/standalone.sh) 5. Log in to management console and add a new deployment. (I tested w/ the wildfly-helloworld.jar from the wildfly/quickstart repo on Github, last commit Jun 20) 6. If you enabled deployment when creating it, disable it now. 7. Make note of the size of the standalone.xml configuration file (~20k) 8. Replace the deployment with the same .jar file 9. Notice the size of the standalone.xml configuration file (~5k)
    • Affects:
      Compatibility/Configuration

      Description

      When replacing a deployment that is disabled at the time of replacement, Wildfly will write out a new configuration .xml that is missing the entire <profile> section, resulting in an application server that is, essentially, non-functional once restarted. There is no obvious effect until restart.

      Also note there is a forum post reporting this behavior from April.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  brian.stansberry Brian Stansberry
                  Reporter:
                  bdaroz Brian Rozmierski
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: