[ 
http://issues.apache.org/jira/browse/GERONIMO-2188?page=comments#action_12421704
 ] 
            
Lin Sun commented on GERONIMO-2188:
-----------------------------------

Re Jenck's email:

Yes with the generic tranql wrapper, setting the commitBeforeAutocommit to true 
would force the commit happen right away.

However this commitBeforeAutocommit isn't available for tranql XA oracle 
wrapper.  For Oracle wrapper's LocalMCF, I can just change:

super(new OracleDataSource(), new OracleExceptionSorter(), false);

to

super(new OracleDataSource(), new OracleExceptionSorter(), true);

However, for Oracle wrapper's XAMCF class, the parent class 
AbstractXADataSourceMCF's contructor only takes the first 2 parms. Here are two 
options I can think of:  

1st option: add the "boolean commitBeforeAutocommit" parm into the 
AbstractXADataSourceMCF's contructor, which will also require changes to the 
localTransactionCommit method in ManagedXAConnection.   Also all the other 
vendor wrappers (db2, derby, mysql) will have to be updated.

2nd option: create the OracleManagedXAConnection class that extends 
AbstractManagedConnection.

I would vote for 1st option as we have a quite big number of buggy database 
vendors.   What do you think?

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

        

Reply via email to