The related datasource file :
<?xml version="1.0" encoding="UTF-8"?> <datasources> <local-tx-datasource> <!-- Setting this to false will bind the DataSource into global jndi --> <use-java-context>false</use-java-context> <jndi-name>Test/DataSource/Data</jndi-name> <connection-url>jdbc:oracle:thin:@localhost:1521:XE</connection-url> <driver-class>oracle.jdbc.driver.OracleDriver</driver-class> <user-name>username</user-name> <password>password</password> <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name> <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name> <min-pool-size>2</min-pool-size> <max-pool-size>20</max-pool-size> <blocking-timeout-millis>5000</blocking-timeout-millis> <idle-timeout-minutes>10</idle-timeout-minutes> <prefill>true</prefill> <metadata> <type-mapping>Oracle9i</type-mapping> </metadata> </local-tx-datasource> </datasources>
Also the ojdbc14.jar file is in the server/default/lib folder
The code works fine using Mysql or SQL Server datasources.
I found a similar post ( http://www.jboss.com/index.html?module=bb&op=viewtopic&t=87423 ) but it is not answered.
thanks in advance
Please post more of the stack trace - the first line is not sufficient. From what you posted I cannot tell if the issue is with the JDBC driver (which is what I would guess) or with some code in JBoss (not likely because as you said "The code works fine using Mysql or SQL Server datasources").
Also, what JDBC driver are you using for Oracle?
Thanks for the quick answer.
This is the full stack trace I get (except the line referring to the calling code).
I should have mentioned that the code is called from a remote client and that the metadata.getColumns() function works fine inside a session bean.
The driver is the one provided by Oracle : Oracle JDBC driver 10.2.0.1.0
There are issues with accessing a data source from a remote client. Looks like you just ran into one of them.
I would guess that there is some issue with serializing an object that the JDBC driver created. Try adding the JDBC driver JAR file to your client's classpath. If that doesn't work, you will have to debug the problem to determine the actual cause and then decide how to fix it.