[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=comments#action_12421535 ] Mario Ruebsam commented on GERONIMO-2188: -----------------------------------------
CommitBeforeAutoCommit = true is a setting in the database pool deployment plan and should only be set for drivers that don't commit when calling setAutoCommit on the connection and this AutoCommit value changed. further discussion about the problem here: http://www.mail-archive.com/user@geronimo.apache.org/msg03450.html JDBC drivers with that problem are: MySQL, MaxDB, PostgreSQL and for what I can see and test atm Oracle with some connection types. I don't know if the OracleXADataSource support the CommitBeforeAutoCommit setting in the deployment plan. > 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
