You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Krishnakumar B (JIRA)" <de...@geronimo.apache.org> on 2006/07/13 13:15:32 UTC
[jira] Created: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
----------------------------------------------------------------------------
Key: GERONIMO-2188
URL: http://issues.apache.org/jira/browse/GERONIMO-2188
Project: Geronimo
Type: Bug
Security: public (Regular issues)
Components: connector
Versions: 1.1.1
Reporter: Krishnakumar B
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-2188) When oracle wrapper is used,
commits are not immediately committed to oracle database
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun reassigned GERONIMO-2188:
---------------------------------
Assignee: David Jencks (was: Lin Sun)
> 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.
[jira] Commented: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "Lin Sun (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=comments#action_12421704 ]
Lin Sun commented on GERONIMO-2188:
-----------------------------------
Re Jenck's email:
Yes with the generic tranql wrapper, setting the commitBeforeAutocommit to true would force the commit happen right away.
However this commitBeforeAutocommit isn't available for tranql XA oracle wrapper. For Oracle wrapper's LocalMCF, I can just change:
super(new OracleDataSource(), new OracleExceptionSorter(), false);
to
super(new OracleDataSource(), new OracleExceptionSorter(), true);
However, for Oracle wrapper's XAMCF class, the parent class AbstractXADataSourceMCF's contructor only takes the first 2 parms. Here are two options I can think of:
1st option: add the "boolean commitBeforeAutocommit" parm into the AbstractXADataSourceMCF's contructor, which will also require changes to the localTransactionCommit method in ManagedXAConnection. Also all the other vendor wrappers (db2, derby, mysql) will have to be updated.
2nd option: create the OracleManagedXAConnection class that extends AbstractManagedConnection.
I would vote for 1st option as we have a quite big number of buggy database vendors. What do you think?
Lin
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-2188
> URL: http://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
> Assigned To: Donald Woods
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun reassigned GERONIMO-2188:
---------------------------------
Assignee: Lin Sun (was: Matt Hogstrom)
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> 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.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.
[jira] Assigned: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "Donald Woods (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=all ]
Donald Woods reassigned GERONIMO-2188:
--------------------------------------
Assign To: Donald Woods
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-2188
> URL: http://issues.apache.org/jira/browse/GERONIMO-2188
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: connector
> Versions: 1.1.1
> Reporter: Krishnakumar B
> Assignee: Donald Woods
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "Donald Woods (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=comments#action_12421227 ]
Donald Woods commented on GERONIMO-2188:
----------------------------------------
Attaching source email thread from user@geronimo -
-------- Original Message --------
Subject: Re: daytrader with Tranql Oracle XA resource adapter
Date: Fri, 7 Jul 2006 09:38:32 -0700
From: David Jencks <da...@yahoo.com>
Reply-To: user@geronimo.apache.org
To: user@geronimo.apache.org
References: <00...@raleigh.ibm.com>
Can you (or have you already) try using the generic tranql wrapper
with the oracle Driver class and set the commitBeforeAutocommit
property to true? This definitely _ought_ to make the commit happen
immediately: if it does, the oracle driver has a bug and we need to
modify the oracle wrapper to work around it.
thanks
david jencks
On Jul 7, 2006, at 8:25 AM, Lin Sun wrote:
> Hi there,
>
> Thanks for the pointer! IIUC, if the application uses
> connection.commit,
> tranql will translate that as setautocommit(true) when the
> commitBeforeAutoCommit is set to false. I believe this is what I
> have in
> my environment.
>
> However, I still don't understand why it makes such a big
> difference for
> Oracle. I have loaded daytrader on another J2EE application server
> (WebSphere Application Server) and found out the same order
> committed to the
> oracle database right away. With that, I would not categorize it
> as one of
> the problematic drivers you mentioned before.
>
> Since derby and db2 XA adapter don't have this "delayed committing"
> problem
> at all, I compared the two Tranql vendors' code with the Oracle
> vendor code.
> Basically the vendor code contains the vendor specific MCF class
> that is
> created based on the datasource from the vendor (for example,
> OracleXADataSource). The MCF also sets/gets the datasource's
> different
> properties (like databasename, username, password, servername,
> etc.). I
> still don't get much clue as to why Oracle is special with Tranql.
>
> I think what I'll do is to come up with a simple application that
> can be
> loaded into Eclipse and step into the connection.commit() code from
> Eclipse.
> Too bad that I haven't figured out how to get daytrader running from
> Eclipse.:-(
>
> Time to study the new plugin Sachin puts out.:-)
>
> Lin
>
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-2188
> URL: http://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
> Assigned To: Donald Woods
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-2188) When oracle wrapper is used, commits
are not immediately committed to oracle database
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated GERONIMO-2188:
-----------------------------------
Attachment: G2188-2.patch
I think this patch is simpler and makes the local and xa implementations more similar. Lin, could you see if it works? I also recently added an m2 build to the tranql oracle connectors and changed the oracle version to 10.2.0.2.
If we can verify this works I'll commit the patch and push snapshots
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> 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
> Assigned To: Matt Hogstrom
> Attachments: G2188-2.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.
[jira] Commented: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467397 ]
Lin Sun commented on GERONIMO-2188:
-----------------------------------
Hi David, Finally able to verify the patch but it didn't work. It acted as if the patch isn't there - transaction aren't committed to the database right away - I was doing query on the order (like select * from orderejb where account_accountid=203;)
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> 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
> Assigned To: Matt Hogstrom
> Attachments: G2188-2.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.
[jira] Commented: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=comments#action_12421370 ]
Matt Hogstrom commented on GERONIMO-2188:
-----------------------------------------
I created a 1.2.1-SNAPSHOT branch of TranQL Connector and changed the CommitBeforeAutoCommit to true. This is available from Codehaus.
Before making this change permanent I'd like to understand if this is really an Oracle bug or if we're interpreting this incorrectly.
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-2188
> URL: http://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
> Assigned To: Donald Woods
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "Mario Ruebsam (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=comments#action_12421535 ]
Mario Ruebsam commented on GERONIMO-2188:
-----------------------------------------
CommitBeforeAutoCommit = true is a setting in the database pool deployment plan and should only be set for drivers that don't commit when calling setAutoCommit on the connection and this AutoCommit value changed.
further discussion about the problem here:
http://www.mail-archive.com/user@geronimo.apache.org/msg03450.html
JDBC drivers with that problem are: MySQL, MaxDB, PostgreSQL and for what I can see and test atm Oracle with some connection types.
I don't know if the OracleXADataSource support the CommitBeforeAutoCommit setting in the deployment plan.
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-2188
> URL: http://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
> Assigned To: Donald Woods
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2188) When oracle wrapper is used,
commits are not immediately committed to oracle database
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525959 ]
David Jencks commented on GERONIMO-2188:
----------------------------------------
I'm confused since it looks to me as if I applied these changes to tranql/connector trunk a long time ago. What did you want me to apply this patch to?
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: 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.
[jira] Assigned: (GERONIMO-2188) When oracle wrapper is used,
commits are not immediately committed to oracle database
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks reassigned GERONIMO-2188:
--------------------------------------
Assignee: Lin Sun (was: David Jencks)
> 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.
[jira] Commented: (GERONIMO-2188) When oracle wrapper is used,
commits are not immediately committed to oracle database
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-2188) When oracle wrapper is used,
commits are not immediately committed to oracle database
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-2188) When oracle wrapper is used,
commits are not immediately committed to oracle database
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (GERONIMO-2188) When oracle wrapper is used,
commits are not immediately committed to oracle database
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun updated GERONIMO-2188:
------------------------------
Summary: When oracle wrapper is used, commits are not immediately committed to oracle database (was: Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle)
> 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.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.
[jira] Assigned: (GERONIMO-2188) When oracle wrapper is used,
commits are not immediately committed to oracle database
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun reassigned GERONIMO-2188:
---------------------------------
Assignee: David Jencks (was: Lin Sun)
David, could ou look at it and get it committed to tranql? Thanks. 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: 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.
[jira] Updated: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "Lin Sun (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=all ]
Lin Sun updated GERONIMO-2188:
------------------------------
Attachment: G2188.patch
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-2188
> URL: http://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
> Assigned To: Donald Woods
> Attachments: 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2188) When oracle wrapper is used,
commits are not immediately committed to oracle database
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525490 ]
Lin Sun commented on GERONIMO-2188:
-----------------------------------
This bug still exists with geronimo 2.0.1 with the same behavior. Working on setting up an env for this.
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> 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.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.
[jira] Commented: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=comments#action_12421681 ]
Matt Hogstrom commented on GERONIMO-2188:
-----------------------------------------
Thanks Mario, I was thinking about it over the weekend and I decided the change was not relevant. Since people can tweak the property they should do that ... I'm going to reverse the change. Might be nice to put out a warning though if we know this is an Oracle driver instead.
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-2188
> URL: http://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
> Assigned To: Donald Woods
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "Lin Sun (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=comments#action_12422466 ]
Lin Sun commented on GERONIMO-2188:
-----------------------------------
I went ahead and implemented the option 1. I decided to add 1 AbstractXADataSourceMCF constructor that takes 3 parms and keep the existing AbstractXADataSourceMCF constructor untouched. I also added 2 constructors for the ManagedXAConnection class with the additional commitBeforeAutoCommit parm at the end. This way the change won't affect other vendors' wrapper.
The change are in both connector and oracle wrapper.
I have tested the change with oracle (XA and local) wrappers, and DB2 XA wrapper, using the daytrader sample. All are working fine and I see orders immediately committed to the orderejb table.
Please review and apply the patch to Tranql.
Thanks, Lin
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-2188
> URL: http://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
> Assigned To: Donald Woods
> Attachments: 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-2188) Need to configure
CommitBeforeAutoCommit=true for Database Commits in Oracle
Posted by "Donald Woods (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=all ]
Donald Woods reassigned GERONIMO-2188:
--------------------------------------
Assignee: Matt Hogstrom (was: Donald Woods)
> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-2188
> URL: http://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
> Assigned To: Matt Hogstrom
> Attachments: 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2188) When oracle wrapper is used,
commits are not immediately committed to oracle database
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526162 ]
Lin Sun commented on GERONIMO-2188:
-----------------------------------
Hi David, check the G2188-latest.patch file, which contains what I propose. Seems you applied portions of it in tranql trunk and that portion didn't make things work yet.
Please let me know if you have any other questions, Thanks, 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: 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.