Hi Igor, Thanks for the detailed info.
I am using JBOSS 3 and it does not have any oracle-xa-service.xml in jca dir. Is it a must to move to 3.0.1RC1? I checked out the Bug Details as well. It seems to me that I need to comment out a for loop in TxCapsule.java //for (int i = 0; i < resourceCount; ++i) + //{ + // if (resourceSameRM[i] == -1 && xaRes.isSameRM(resources[i])) + // { + // // The xaRes is new. We register the xaRes with the Xid + // // that the RM has previously seen from this transaction, + // // and note that it has the same RM. + // startResource(addResource(xaRes, resourceXids[i], i)); + // + // return true; + // } + //} //} Are there any other problems with using ORACLE? I am using Oracle9i. TIA, Saroj -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Igor Fedorenko Sent: Friday, July 26, 2002 7:03 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Jboss 3 with ORACLE 8.0.5+ Saroj Kumar wrote: > Hi All, > > I want to know all the steps required to configure ORACLE 8+/8i/9i to > work with JBOSS3. > > It would be better if someone could explain the pre-requisites and > necessary groundwork to be done to make it work. > > TIA, > Saroj There are two possible ways to configure Oracle datasource (and two example config files in $JBOSS_HOME/docs/examples/jca). As somebody has already mentioned on this list you could use oracle-service.xml as a starting point, set connectionUrl, username/password and drop the file into $JBOSS_HOME/server/default/deploy. This way you configure datasource for local transactions only (for example, you cannot have a transaction that includes both jms session and database connection). I would not recommend this configuration for production but it might be acceptible during development. If you do need global transaction then you should go with oracle-xa-service.xml, however, configuration procedure is a bit more complicated and there is an outstanding compatibility issue that has to be resolved (see bug 585632 on SF). To configure xa datasource Pre-requisites 1. Your oracle server must be java-enabled (if java is installed, following query returns non-zero result when executed from sqlplus select count(*) from all_objects where object_type like 'JAVA%'; 2. JBoss 3.0.1RC1 (you probably need to checkout and compile Branch_3_0 from cvs) 3. Bug 585632 is fixed. As a workaround you could try to use my patch for the bug, but it could cause problems with other non-oracle resource managers. Configuration 1. Edit $JBOSS_HOME/server/default/conf/jboss-service.xml, find "jboss:service=XidFactory" mbean definition and add "<attribute name="Pad">true</attribute>" to it. Mbean definition should look like <mbean code="org.jboss.tm.XidFactory" name="jboss:service=XidFactory"> <attribute name="Pad">true</attribute> </mbean> 2. Copy $JBOSS_HOME/docs/examples/jca/oracle-xa-service.xml to $JBOSS_HOME/server/default/deploy. Edit the file and remove "jboss:service=XidFactory" mbean from it. You should also configure database url, username and password. Both xa and non-xa configurations require classes12.zip (oracle jdbc driver) to be put in $JBOSS_HOME/server/default/lib. -- Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user