[
https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527583
]
Lin Sun commented on GERONIMO-2188:
-----------------------------------
David,
I think I know where the confusion is now. Geronimo 2.0 or 2.0.1 uses tranql
connector 1.3, which is where I started to look at the prob as that is the code
base I use to recreate it. So the patch I submitted is created against the
tagged version of connector 1.3, which surprisingly was created sometime last
year (I assumed it was fairly recently but I am wrong.) I just went to tranql
connector trunk, which did have all the changes there.
I think to resolve this, we just need to get a newer version of tranql out.
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: Lin Sun
> 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.
