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

data-source:enable is broken

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 9.0.0.Beta1
    • 8.0.0.Final, 8.1.0.Final, 9.0.0.Alpha1
    • JCA
    • None
    • Hide

      In domain mode

      1. /profile=full/subsystem=datasources/data-source=foo:add(jndi-name=java:jboss/datasources/foo,driver-name=h2,connection-url=jdbc:h2:mem:foo,enabled=false)
      2. /profile=full/subsystem=datasources/data-source=foo:enable(){allow-resource-service-restart=true}
      3. /profile=full/subsystem=datasources/data-source=foo:read-attribute(name=enabled) returns false
      4. reload --host=master --restart-servers=true
      5. /profile=full/subsystem=datasources/data-source=foo:read-attribute(name=enabled) still returns false
      Show
      In domain mode /profile=full/subsystem=datasources/data-source=foo:add(jndi-name=java:jboss/datasources/foo,driver-name=h2,connection-url=jdbc:h2:mem:foo,enabled=false) /profile=full/subsystem=datasources/data-source=foo:enable(){allow-resource-service-restart=true } /profile=full/subsystem=datasources/data-source=foo:read-attribute(name=enabled) returns false reload --host=master --restart-servers=true /profile=full/subsystem=datasources/data-source=foo:read-attribute(name=enabled) still returns false
    • Hide

      :write-attribute(name=enabled, value=true) works as expected.

      Show
      :write-attribute(name=enabled, value=true) works as expected.

    Description

      Enabling a disabled datasource using the operation :enable() is broken. It remains disabled.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. HAL-510 WildFly datasource shows disabled even after enabling

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-2986 cli batch incorrect handling of the enabled attribute during datasource creation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-3166 can't enable datasource both via console or CLI with cluster mode(can't persist to domain.xml)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. WFLY-2833 data-source:enalbe and datasource:write-attribute(name=enabled, value=true) should have same result

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              smaestri@redhat.com Stefano Maestri
              hpehl@redhat.com Harald Pehl
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: