[
https://issues.jboss.org/browse/JBJCA-990?page=com.atlassian.jira.plugin....
]
Jesper Pedersen updated JBJCA-990:
----------------------------------
Summary: TestConnection override with CRI and Subject (was: Test connection
through CLI when <allow-multiple-users/> is applied to a datasource)
Description: Create an override of the test connection method which operates on passed
in ConnectionRequestInfo and Subject objects (was: Create a XA data-source(via CLI) which
has the attribute <allow-multiple-users/> defined to true.
Testing the connection using CLI shows the below error -
**************************************
[standalone@localhost:9999 /]
/subsystem=datasources/xa-data-source=OracleXA_DS:test-connection-in-pool()
{
"outcome" => "failed",
"failure-description" => "JBAS010440: failed to invoke operation:
JBAS010447: Connection is not valid",
"rolled-back" => true
}
**************************************
On checking the description of the attribute (
/subsystem=datasources/xa-data-source=OracleXA_DS:read-resource-description(recursive=true)
) it says -
"allow-multiple-users" => {
"type" => BOOLEAN,
"description" => "Specifies if multiple users will
access the datasource through the getConnection(user, password) method and hence if the
internal pool type should account for that"
When testing the connection through "test-connection-in-pool" there is no way to
provide username/password for the above mentioned getConnection() and hence connection
fails.)
Component/s: Core
(was: JDBC)
TestConnection override with CRI and Subject
--------------------------------------------
Key: JBJCA-990
URL:
https://issues.jboss.org/browse/JBJCA-990
Project: IronJacamar
Issue Type: Feature Request
Components: Core
Affects Versions: 1.0.13.Final
Environment: JBoss EAP 6.0.1
JBoss AS 7.1.3
Reporter: Anurag Debnath
Assignee: Jesper Pedersen
Labels: eap6
Create an override of the test connection method which operates on passed in
ConnectionRequestInfo and Subject objects
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira