Please post your *-ds.xml file. Also, make sure that the jdbc.jar files that are in your server/lib directory are the *only* Jar files. Also, you don't need both the zip and the jar. Just use the ojdbc14.jar file and remove the classes.zip.
I used the standard oracle-ds.xml from the example/jca
<datasources> <local-tx-datasource> <jndi-name>OracleDS</jndi-name> <connection-url>jdbc:oracle:thin:@youroraclehost:1521:yoursid</connection-url> <!-- Here are a couple of the possible OCI configurations. For more information, see http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/java.920/a96654/toc.htm <connection-url>jdbc:oracle:oci:@youroracle-tns-name</connection-url> or <connection-url>jdbc:oracle:oci:@(description=(address=(host=youroraclehost)(protocol=tcp)(port=1521))(connect_data=(SERVICE_NAME=yourservicename)))</connection-url> Clearly, its better to have TNS set up properly. --> <driver-class>oracle.jdbc.driver.OracleDriver</driver-class> <user-name>x</user-name> <password>y</password> <!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool --> <!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name--> <!-- Checks the Oracle error codes and messages for fatal errors --> <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name> <!-- sql to call when connection is created <new-connection-sql>some arbitrary sql</new-connection-sql> --> <!-- sql to call on an existing pooled connection when it is obtained from pool - the OracleValidConnectionChecker is prefered <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql> --> <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) --> <metadata> <type-mapping>Oracle9i</type-mapping> </metadata> </local-tx-datasource> </datasources Changing the values, i do however have the .zip and the .jar in the server/lib directory.
I have same problem. But second and later tries are successful.
I guess there is problem to detect if Oracle jdbc driver is loaded.
This generally happens when you have your JDBC driver jar files inside another deployable unit (WAR, EAR) and not in server/lib. It is a ClassLoader issue with the DriverManager in the VM, not in JBossAS.
Thanks for replay. I think so.
For information: I've rewrited my-ds.xml to use xa-datasource with oracle, it's work without exceptions now.