[ https://issues.jboss.org/browse/WFLY-2403?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2403: ----------------------------------------------- Martin Simka <msimka(a)redhat.com&gt; made a comment on [bug 970679|https://bugzilla.redhat.com/show_bug.cgi?id=970679] @Brian: I've just never noticed this behavior. It isn't regression. @Stefano: I can't reproduce this issue on EAP 6.1.0? Any idea what I'm doing wrong? EAP 6.1.0 Steps to Reproduce: 1.Create a Datasource of XADatasource [standalone@localhost:9999 /] data-source add --name=Test2 --driver-name=h2 --jndi-name=java:jboss/datasources/Test2 --connection-url=jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1 2.Disable it [standalone@localhost:9999 /] data-source disable --name=Test2 operation-requires-reload true process-state reload-required 3.The response indicates a server reload is required 4.Execute the reload operation [standalone@localhost:9999 /] reload Actual results: The datasource is back to enabled state Expected results: The datasource should be in disabled state ^------ this is not true, datasource is disabled [standalone@localhost:9999 /] /subsystem=datasources/data-source=Test2:read-attribute(name=enabled) { "outcome" => "success", "result" => false } EAP 6.1.1 Steps to Reproduce: 1.Create a Datasource of XADatasource [standalone@localhost:9999 /] data-source add --name=Test2 --driver-name=h2 --jndi-name=java:jboss/datasources/Test2 --connection-url=jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1 2.Disable it [standalone@localhost:9999 /] data-source disable --name=Test2 operation-requires-reload true process-state reload-required 3.The response indicates a server reload is required 4.Execute the reload operation [standalone@localhost:9999 /] reload Actual results: The datasource is back to enabled state Expected results: The datasource should be in disabled state ^-- this is not true, datasource is disabled [standalone@localhost:9999 /] /subsystem=datasources/data-source=Test2:read-attribute(name=enabled) { "outcome" => "success", "result" => false } EAP 6.2.0.CR1 Steps to Reproduce: 1.Create a Datasource of XADatasource [standalone@localhost:9999 /] data-source add --name=Test2 --driver-name=h2 --jndi-name=java:jboss/datasources/Test2 --connection-url=jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1 2.Disable it [standalone@localhost:9999 /] data-source disable --name=Test2 operation-requires-reload true process-state reload-required 3.The response indicates a server reload is required 4.Execute the reload operation [standalone@localhost:9999 /] reload Actual results: The datasource is back to enabled state Expected results: The datasource should be in disabled state ^-- this is not true, datasource is disabled [standalone@localhost:9999 /] /subsystem=datasources/data-source=Test2:read-attribute(name=enabled) { "outcome" => "success", "result" => false } The same with EAP 6.1.0 [standalone@localhost:9999 /] /subsystem=datasources/data-source=Test2:add(connection-url=jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1, jndi-name=java:jboss/datasources/Test2, driver-name=h2) {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=datasources/data-source=Test2:disable() { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } [standalone@localhost:9999 /] reload [standalone@localhost:9999 /] /subsystem=datasources/data-source=Test2:read-attribute(name=enabled) { "outcome" => "success", "result" => false } I'm getting same result when I add step enable after creation of datasource. EAP 6.1.0 [standalone@localhost:9999 /] data-source add --name=Test2 --driver-name=h2 --jndi-name=java:jboss/datasources/Test2 --connection-url=jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1 [standalone@localhost:9999 /] data-source enable --name=Test2 [standalone@localhost:9999 /] data-source disable --name=Test2 operation-requires-reload true process-state reload-required [standalone@localhost:9999 /] reload [standalone@localhost:9999 /] /subsystem=datasources/data-source=Test2:read-attribute(name=enabled) { "outcome" => "success", "result" => false } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira