[jboss-jira] [JBoss JIRA] Commented: (AS7-1232) :test-connection-in-pool is "useless"
[
https://issues.jboss.org/browse/AS7-1232?page=com.atlassian.jira.plugin.s...
]
Stefano Maestri commented on AS7-1232:
--------------------------------------
the problem is due to a wrong jndi name generation when ds are registered in ana internal
management repository to call runtime operation.
Fixed and pull request asked. Please note that now we have 3 possible answer for this
operation:
"outcome" => "failed",
"failure-description" => "failed to set invoke operation: failed to
match pool. Check JndiName: java:jboss/datrces/ExampleDS",
"rolled-back" => true
OR
"outcome" => "success",
"result" => [true]
OR
"outcome" => "success",
"result" => [false]
Last one is saying: "operation invoked, but connection tested is not valid" that
should be your case.
:test-connection-in-pool is "useless"
-------------------------------------
Key: AS7-1232
URL: https://issues.jboss.org/browse/AS7-1232
Project: Application Server 7
Issue Type: Bug
Components: JCA
Affects Versions: 7.0.0.CR1
Reporter: Heiko Rupp
Assignee: Stefano Maestri
I have defined a datasource like this:
[domain@localhost:9999 data-source=postresDS] :read-resource
{
"outcome" => "success",
"result" => {
"connection-url" => "jdbc:yadayada",
"driver-name" => "postgresql-9.0-801.jdbc4.jar",
So obviously with an invalid driver.
But still I get
[domain@localhost:9999 data-source=postresDS] :test-connection-in-pool
{
"outcome" => "success",
"result" => undefined
}
which makes imho no sense.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira