[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=comments#action_12421227 ] Donald Woods commented on GERONIMO-2188: ----------------------------------------
Attaching source email thread from [EMAIL PROTECTED] - -------- Original Message -------- Subject: Re: daytrader with Tranql Oracle XA resource adapter Date: Fri, 7 Jul 2006 09:38:32 -0700 From: David Jencks <[EMAIL PROTECTED]> Reply-To: [email protected] To: [email protected] References: <[EMAIL PROTECTED]> Can you (or have you already) try using the generic tranql wrapper with the oracle Driver class and set the commitBeforeAutocommit property to true? This definitely _ought_ to make the commit happen immediately: if it does, the oracle driver has a bug and we need to modify the oracle wrapper to work around it. thanks david jencks On Jul 7, 2006, at 8:25 AM, Lin Sun wrote: > Hi there, > > Thanks for the pointer! IIUC, if the application uses > connection.commit, > tranql will translate that as setautocommit(true) when the > commitBeforeAutoCommit is set to false. I believe this is what I > have in > my environment. > > However, I still don't understand why it makes such a big > difference for > Oracle. I have loaded daytrader on another J2EE application server > (WebSphere Application Server) and found out the same order > committed to the > oracle database right away. With that, I would not categorize it > as one of > the problematic drivers you mentioned before. > > Since derby and db2 XA adapter don't have this "delayed committing" > problem > at all, I compared the two Tranql vendors' code with the Oracle > vendor code. > Basically the vendor code contains the vendor specific MCF class > that is > created based on the datasource from the vendor (for example, > OracleXADataSource). The MCF also sets/gets the datasource's > different > properties (like databasename, username, password, servername, > etc.). I > still don't get much clue as to why Oracle is special with Tranql. > > I think what I'll do is to come up with a simple application that > can be > loaded into Eclipse and step into the connection.commit() code from > Eclipse. > Too bad that I haven't figured out how to get daytrader running from > Eclipse.:-( > > Time to study the new plugin Sachin puts out.:-) > > Lin > > Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle > ---------------------------------------------------------------------------- > > Key: GERONIMO-2188 > URL: http://issues.apache.org/jira/browse/GERONIMO-2188 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: connector > Affects Versions: 1.1.1 > Reporter: Krishnakumar B > Assigned To: Donald Woods > > We have to configure CommitBeforeAutCommit="true" property exclusively in the > database connection pool plan, to have the ejb -based transactions > immediately committed for oracle database. Otherwise it only commits > transaction when the server shuts-down. This problem is not faces with > Derby database. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
