-
Bug
-
Resolution: Done
-
Major
-
None
-
None
When a data-source was failed to be added because of missing connection-properties:
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
, it can be added by correcting the information, like:
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test") {"outcome" => "success"}
But the test-connection-in-pool() operation failed with IllegalStateException of the new created data-source:
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool() { "outcome" => "failed", "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid", "rolled-back" => true }
Changing the Step 1 to:
/subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2)
for the verifying, because of with fixing of https://issues.jboss.org/browse/JBJCA-1331 (also fixed in ironjacamar-1.3.5.Final), the original step 1 will not cause problems any more.
- incorporates
-
JBJCA-1334 Add DataSource to ManagementRepository only after deployed successfully
- Resolved
- is cloned by
-
JBEAP-6592 (7.0.z) JBJCA-1334 - Add DataSource to ManagementRepository only after deployed successfully
- Closed
-
WFLY-7214 Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition
- Closed
- is incorporated by
-
JBEAP-6133 (7.1.0) Upgrade to IronJacamar 1.4.0 when released
- Closed