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] Commented: (GERONIMO-2188) When oracle wrapper is used, commits are not immediately committed to oracle database
Date Fri, 14 Sep 2007 14:45:34 GMT

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

David Jencks commented on GERONIMO-2188:
----------------------------------------

I'm mystified as to what you want me to do.  AFAICT the entire patch G2188-latest.patch was
applied many months ago to trunk.  Could you please provide a patch against current trunk?
 If you have all of tranql checked out the best would be to make the patch from the file system
location corresponding to https://svn.codehaus.org/tranql  (the root of the tranql checkout)
so it's really clear where the changes go.

> 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.


Mime
View raw message