geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Sun (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-2188) When oracle wrapper is used, commits are not immediately committed to oracle database
Date Mon, 17 Sep 2007 19:18:44 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528121
] 

Lin Sun commented on GERONIMO-2188:
-----------------------------------

Verified this is fixed in tranql connector trunk and oracle vendor wrapper trunk.   This defect
should be closed whenever we release a newer version of tranql vendor wrappers and the connector
jar and the generic wrapper and we change geronimo to use them.  Assign back to David for
his help on releasing newer versions of tranql artifacts.   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: 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.


Mime
View raw message