-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
When a new datasource is created with enabled=false, the :test-connection-in-pool operation fails. You can reproduce the error using the following CLI commands:
Enabled by default
[standalone@localhost:9990 /] /subsystem=datasources/data-source=foo:add(jndi-name=java:/foo,driver-name=h2,connection-url=jdbc:h2:mem:foo) {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=datasources/data-source=foo:test-connection-in-pool { "outcome" => "success", "result" => [true] }
Disabled by default
[standalone@localhost:9990 /] /subsystem=datasources/data-source=foo:add(jndi-name=java:/foo,driver-name=h2,connection-url=jdbc:h2:mem:foo,enabled=false) {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=datasources/data-source=foo:test-connection-in-pool { "outcome" => "failed", "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0042: failed to match pool. Check JndiName: java:/foo", "rolled-back" => true }
- causes
-
HAL-617 Test connection fails every time
- Resolved