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] Updated: (GERONIMO-2188) When oracle wrapper is used, commits are not immediately committed to oracle database
Date Sat, 08 Sep 2007 20:06:29 GMT

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

Lin Sun updated GERONIMO-2188:
------------------------------

    Attachment: G2188-latest.patch

David, I reapplied your patch onto tranql-connector 1.3 and it did work!    Attached is the
patch generated with latest  tranql-connector 1.3 tree.    

It took me a while to figure this out.  First I only replace the oracle vendor wrapper with
the one I built then deploy the daytrader app but the connector. 1.3.jar didn't get used.
 Thus I replaced the connector 1.3.jar with all the connector 13.jar I can find in the repo
- configs\system-database\2.0.1\system-database-2.0.1.car\rar and configs\uddi-tomcat\2.0.1\uddi-tomcat-2.0.1.car\uddi-db
and I started to see the new code take place which does the commits right away,

> 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