-
Bug
-
Resolution: Done
-
Minor
-
7.0.0.GA
-
None
-
-
-
-
-
-
Workaround Exists
-
-
Below is the result of add .. remove ..add operation of XADatasource .
1. Add - OK
[domain@localhost:9990 /] ./profile=default/subsystem=datasources/xa-data-source=TestXADataSource:add(jndi-name=java\:jboss\/datasources\/oracleXaDatasource,driver-name=oracle-driver.jar) { "outcome" => "success", "result" => undefined, "server-groups" => undefined }
2. Remove - OK
[domain@localhost:9990 /] ./profile=default/subsystem=datasources/xa-data-source=TestXADataSource:remove() { "outcome" => "success", "result" => undefined, "server-groups" => undefined }
3. Add - Error is thrown
[domain@localhost:9990 /] ./profile=default/subsystem=datasources/xa-data-source=TestXADataSource:add(jndi-name=java\:jboss\/datasources\/oracleXaDatasource,driver-name=oracle-driver.jar) { "outcome" => "failed", "failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.data-source.TestXADataSource' is already registered in context 'profile=default'."}, "rolled-back" => true }
- is cloned by
-
JBEAP-6050 Removing XA Datasources via CLI OR DMR does not de-register it from the context without reload.
- Closed
-
WFLY-7129 Removing XA Datasources via CLI OR DMR does not de-register it from the context without reload.
- Closed