[jira] Assigned: (GERONIMO-2188) When oracle wrapper is used, commits are not immediately committed to oracle database
[ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun reassigned GERONIMO-2188: - Assignee: David Jencks (was: Lin Sun) When oracle wrapper is used, commits are not immediately committed to oracle database - Key: GERONIMO-2188 URL: https://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 Assignee: David Jencks Attachments: G2188-2.patch, G2188-latest.patch, G2188.patch 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. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-2188) When oracle wrapper is used, commits are not immediately committed to oracle database
[ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun reassigned GERONIMO-2188: - Assignee: David Jencks (was: Lin Sun) David, could ou look at it and get it committed to tranql? Thanks. Lin When oracle wrapper is used, commits are not immediately committed to oracle database - Key: GERONIMO-2188 URL: https://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 Assignee: David Jencks Attachments: G2188-2.patch, G2188-latest.patch, G2188.patch 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. - You can reply to this email to add a comment to the issue online.
