Are you using jboss 3?
If you look at jndiview can you see your datasource bound?
If you look at the server log, is the oracle service.xml deployed before your app?
Are there any errors in the log?
I had a similar problem and I noticed in the startup messages that I was getting a class not found exception for the database driver.
My work-around was to convert the classes.zip file to a classes.jar and drop it into the lib/ext dir...
Still not sure why classes.zip isn't picked up...
Thanks for tips, still a problem. I have reloaded the classes12.zip file as oracle.jar into the lib\ext directory. I am using JBoss 2.4.1, the server log shows oracle.jar being included in the classpath but nowhere else, no errors are displayed. When I try to run the monitor program in JBoss\admin to look at jndi I get a class not found error ie. javax.jms.MessageListener although the jar file containing this is in the classpath.
i had the same problem yesterday (with 2.4.3)...
lib/ext/classes12 is ok.
add the oracle-driver to this entry:
duplicate the sample for hypersonic and change the params for your needs:
hope that helps
Thanks for your help, this seems to do the trick.
I am still confused here. If you modify the jboss.jcml and
add a mbean for a connection pool, it doesn't mean that you solved the data source problem. Here is my oracleds-service.xml and I placed it in jboss_home\deploy. I couldn't see any deploy info from the server.log when I start Jboss and no exception. Can anybody help?
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: oracle-service.xml,v 1.2 2002/01/14 00:16:51 d_jencks Exp $ -->
<!-- oracleds-service.xml -->
<!-- JBoss v3.0alpha (november 23, 2001) ORACLE thin driver Configuration -->
<!-- tested against ORACLE v8.x -->
<!-- ==================================================================== -->
<!-- please put jdbc driver (in this case classes12.zip) in jboss_home/lib/ext -->
<!-- please put this file (oracleds-service.xml) under jboss_home/deploy -->
<!-- Contributed by Christian Biasuzzi firstname.lastname@example.org-->
<!-- ===================================================================== -->
<depends optional-attribute-name="ResourceAdapterName">jboss.jca:service=RARDeployment,name=Minerva JDBC LocalTransaction ResourceAdapter
#Wed Aug 15 16:17:29 EDT 2001
oracle-service.xml is 3.0 ONLY. for 2.4 use the jboss.jcml suggestions. If you are using 3.0 check you have the correct tags for the version of jboss and that the object names in the depends/mbean-ref tags are EXACTLY the object names of the referred mbeans.