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

Deleting ExampleDS Leaves Remnants in standalone.xml

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • 11.0.0.Final
    • JCA
    • Hide

      REPRODUCE

      1. Unpack Wildfly 11.0.0
      2. Delete the example datasource
      3. Configure required datasource for application (deploy driver if required)
      4. Attempt to deploy application needing the newly configured JDBC configuration
      5. Receive deployment error indicating required "Example DS" JDBC resource is unavailable.

      WORKAROUND

      1. Manually delete remaining subsystem configuration from standalone.xml
      2. Restart Wildfly in standalone mode
      3. Deploy application and observe error for required "Example DS" component is no longer thrown
      Show
      REPRODUCE Unpack Wildfly 11.0.0 Delete the example datasource Configure required datasource for application (deploy driver if required) Attempt to deploy application needing the newly configured JDBC configuration Receive deployment error indicating required " Example DS " JDBC resource is unavailable. WORKAROUND Manually delete remaining subsystem configuration from standalone.xml Restart Wildfly in standalone mode Deploy application and observe error for required "Example DS" component is no longer thrown
    • Compatibility/Configuration, User Experience
    • 47700782

      SUMMARY

      When initially installing Wildfly 11.0.0 Final, the installation comes pre-configured with a datasource labeled "Example DS".

      When this datasource is deleted, some configuration for it remains in the standalone.xml file for the standalone server mode.

      WORKAROUND

      Removing this configuration manually and restarting Wildfly in standalone mode resolves the issue. (I tested by searching for "ExampleDS" as a string match in vi and deleting the one line the match found)

      BUG JUSTIFICATION

      1. I would expect anything labeled as "Example" to be deleted by an administrator in most environments
      2. I would expect deleted items to be fully removed upon deletion so remnant configuration couldn't cause issues with unrelated deployments (i.e. deployments which don't specifically require the deleted item)

              rhn-cservice-bbaranow Bartosz Baranowski
              cgiddings_jira Chris Giddings (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: