[
https://issues.jboss.org/browse/WFLY-2898?page=com.atlassian.jira.plugin....
]
Igor Shulika commented on WFLY-2898:
------------------------------------
<subsystem xmlns="urn:jboss:domain:datasources:2.0">
<datasources>
<datasource jndi-name="java:/GOLDDatasource"
pool-name="GOLDDatasource" enabled="true"
use-java-context="true">
<connection-url>jdbc:oracle:thin:@xxxxxx:1521/dev11g</connection-url>
<driver-class>org.jaffa.driver.oracle.OracleDriver</driver-class>
<driver>oracle</driver>
<pool>
<max-pool-size>100</max-pool-size>
</pool>
<security>
<user-name>xxxxx</user-name>
<password>xxxxx</password>
</security>
</datasource>
<xa-datasource jndi-name="java:/GOLDTxDatasource"
pool-name="GOLDTxDatasource" enabled="true"
use-java-context="true">
<xa-datasource-property name="URL">
jdbc:oracle:thin:@xxxxxxxx:1521/dev11g
</xa-datasource-property>
<xa-datasource-property name="User">
xxxxx
</xa-datasource-property>
<xa-datasource-property name="Password">
xxxxx
</xa-datasource-property>
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
<driver>oracle</driver>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
<xa-pool>
<min-pool-size>1</min-pool-size>
<max-pool-size>100</max-pool-size>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
<no-tx-separate-pools>true</no-tx-separate-pools>
<pad-xid>false</pad-xid>
<wrap-xa-resource>true</wrap-xa-resource>
</xa-pool>
<security>
<user-name>xxxxx</user-name>
<password>xxxxxx</password>
</security>
<validation>
<valid-connection-checker
class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>
<validate-on-match>false</validate-on-match>
<background-validation>false</background-validation>
<use-fast-fail>false</use-fast-fail>
<stale-connection-checker
class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>
<exception-sorter
class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>
</validation>
</xa-datasource>
<drivers>
<driver name="oracle"
module="org.jaffa.jdbc.driver.oracle">
<driver-class>org.jaffa.driver.oracle.OracleDriver</driver-class>
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
JNDI Name lookup of the DataSource returns NULL
-----------------------------------------------
Key: WFLY-2898
URL:
https://issues.jboss.org/browse/WFLY-2898
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Naming, Web (Undertow)
Affects Versions: 8.0.0.CR1, 8.0.0.Final
Reporter: Igor Shulika
Assignee: Eduardo Martins
Attachments: 1.PNG, 2.PNG, 3.PNG
Hi,
I'm having a problem to obtain DataSource using JNDI Name lookup.
Please see my code below:
Connection connection = null;
DataSource dataSource = null;
try {
final Context initContext = new InitialContext();
dataSource = (DataSource) initContext.lookup("java:/MyDataSource");
connection = dataSource.getConnection();
} catch (Exception e) {
LOGGER.error(e);
}
I'm doing initContext.lookup from a servlet, everything is working on JBoss EAP
6.2.0.GA (AS 7.3.0.Final-redhat-14).
Also I can find and test connection of my “java:/MyDataSource” under the “Datasources”
section of the WildFly Administration Console just fine(anoter word the datasource is
there).
--
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