geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-2188) When oracle wrapper is used, commits are not immediately committed to oracle database
Date Fri, 28 Sep 2007 21:55:51 GMT

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

David Jencks closed GERONIMO-2188.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.2

I've included the new tranql rars in 2.0.2.  I'm not too sure about the mysql and postgresql
ones so they are still at snapshot, but a working oracle wrapper is inclluded.

> 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
>             Fix For: 2.0.2
>
>         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