[jira] Commented: (GERONIMO-2188) When oracle wrapper is used, commits are not immediately committed to oracle database
[ 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
[ 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] Commented: (GERONIMO-2188) When oracle wrapper is used, commits are not immediately committed to oracle database
[ 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
[ 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.
[jira] Commented: (GERONIMO-2188) When oracle wrapper is used, commits are not immediately committed to oracle database
[ 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.