Using other datasources than DefaultDS in JBoss 3

[stitzl]

Hey,

I'm trying to migrate an app from JBoss 2.4.4 (where it runs w/o any problems) to JBoss 3.0.0RC1. I have some problems configuring the datasources.

The app is accessing an Oracle8i database, and I already downloaded, configured and deployed the oracle-service.xml file. Then I configured my app to use the OracleDS datasource I thought to be created by that service. But I keep getting the following exception:

13:36:40,124 ERROR [EntityContainer] Exception in service lifecyle operation: create
org.jboss.deployment.DeploymentException: OracleDS not bound
at org.jboss.ejb.plugins.jaws.metadata.JawsApplicationMetaData.create(JawsApplicationMetaData.java:137)

I also tried it round the other way, renaming the datasource from oracle-service.xml to DefaultDS (and renaming the original DefaultDS to something else). I get a similar exception, namely that DefaultDS is not bound any longer.

Can anybody give me some directions how to create and bind a datasource to access my DB from JBoss 3?

Thanks a lot in advance,
Lars

[ibruell]

you have to create a oracle-service.xml file like hsqldb-service.xml in the deploy directory.
In cvs are more some examples

[shogun]

I had the same problem, because I had a wrong tag in my mysql-srvice.xml. Check, if your LocalTxCM for your DS is started. Therefor you can use a browser and connect to your jboss over port 8082. You can find the entry under jboss.jca.

Shogun

[ibruell]

Oooh, it seems that i haven't read the whole letter.

I had this error too. I have copied the hsqldb-service.xml and changed the required attributes.

After i have removed
<depends>jboss:service=SAPDB</depends>
it worked.

[stitzl]

Shogun,

thanks a lot, that did it. As you proposed, the LocalTX*-services were not running for the datasource, so I dumped the downloaded example oracle-service.xml - which is WRONG and DOES NOT WORK with the current JBoss 3.0.0RC1 (but how should one figure this one out without the help of such competent advisors? ;)

After that I copied, adjusted and renamed the provided hsqldb-service.xml, as mentioned by ibruell. Now at last the jar deploys fine, but I still have some issues with the JDBC-SQL-mappings...

Thank you all for your quick help - it's always good if other people stumbled over the same errors before.

Cheers, Lars