]
Harald Pehl commented on WFLY-4750:
-----------------------------------
Comment on the related HAL-617 issue from [~mayerw01]:
{quote}
But if this issue is related to "enabled=false by default" shouldn't the
test connection also work if you just enable the datasource manually? When I push the Test
connection on a disabled datasource I get the message "The datasource must be enabled
in order to test the connection", which sounds reasonable. After enable and reload I
get the 'Connection is not valid' message. Increasing the 'Max Pool Size'
(at least to 1 and reload) finally gives me a 'Successfully connected to database
MySqlDS.'
{quote}
When a datasource is created with enabled=false, the
:test-connection-in-pool op fails
--------------------------------------------------------------------------------------
Key: WFLY-4750
URL:
https://issues.jboss.org/browse/WFLY-4750
Project: WildFly
Issue Type: Bug
Components: JCA
Reporter: Harald Pehl
Assignee: Jesper Pedersen
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*
{code}
[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]
}
{code}
*Disabled by default*
{code}
[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
}
{code}