You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/09/08 23:17:29 UTC
[jira] Commented: (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:comment-tabpanel#action_12525959 ]
David Jencks commented on GERONIMO-2188:
----------------------------------------
I'm confused since it looks to me as if I applied these changes to tranql/connector trunk a long time ago. What did you want me to apply this patch to?
thanks
> 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.