From dev-return-21394-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Dec 19 15:39:14 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F34E0D770 for ; Wed, 19 Dec 2012 15:39:13 +0000 (UTC) Received: (qmail 28129 invoked by uid 500); 19 Dec 2012 15:39:13 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 28001 invoked by uid 500); 19 Dec 2012 15:39:13 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 27603 invoked by uid 99); 19 Dec 2012 15:39:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2012 15:39:13 +0000 Date: Wed, 19 Dec 2012 15:39:13 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OPENJPA-2312) H2 is forced to autoCommit; breaks transactions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536043#comment-13536043 ] Kevin Sutter commented on OPENJPA-2312: --------------------------------------- It sounds like your usage should not be container-managed connections and transactions. My past experiences with Spring and OpenJPA seem to have been centered around container-managed, but it sounds like your case is more application-managed (or Spring managed). So, if the setting of this supportsMultipleNontransactionalResultSets property works for you, that's great. I am not an expert with H2, so I don't really know whether the default value for this particular database should be changed or not. If more experienced H2 users can vouch for it, then maybe this default should be changed. But, for the time being and for this JIRA, I would propose that the setting in persistence.xml is a suitable solution/workaround. Agree? Thanks, Kevin > H2 is forced to autoCommit; breaks transactions > ----------------------------------------------- > > Key: OPENJPA-2312 > URL: https://issues.apache.org/jira/browse/OPENJPA-2312 > Project: OpenJPA > Issue Type: Bug > Affects Versions: 2.0.0 > Reporter: Gustavo Lopes > Attachments: details.txt > > > DataSourceFactory::installDBDictionary() sets autocommit to TRUE on the ConfiguringConnectionDecorator because supportsMultipleNontransactionalResultSets is true. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira