Return-Path: X-Original-To: apmail-geronimo-dev-archive@www.apache.org Delivered-To: apmail-geronimo-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 A887699FE for ; Mon, 28 May 2012 03:12:29 +0000 (UTC) Received: (qmail 55722 invoked by uid 500); 28 May 2012 03:12:27 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 55573 invoked by uid 500); 28 May 2012 03:12:26 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 55530 invoked by uid 99); 28 May 2012 03:12:24 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 May 2012 03:12:24 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id A6916142858 for ; Mon, 28 May 2012 03:12:24 +0000 (UTC) Date: Mon, 28 May 2012 03:12:24 +0000 (UTC) From: "David Jencks (JIRA)" To: dev@geronimo.apache.org Message-ID: <84754779.7678.1338174744687.JavaMail.jiratomcat@issues-vm> In-Reply-To: <2092993682.1204.1298013192048.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (GERONIMO-5824) jpa JTA transaction and missing jta-data-source should be warned about or rejected 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/GERONIMO-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284281#comment-13284281 ] David Jencks commented on GERONIMO-5824: ---------------------------------------- Thanks for looking into this. in the persistence.xml you can specify and . In this case only the was specified. However, the datasource configured there should have had in its plan but had either or Openjpa uses the non-jta-datasource for things like creating tables, getting "sequence" values from tables outside a jta transaction, and similar things. It uses the connection.commit style of local transaction management which causes exceptions if the connection is already enrolled in an XA transaction since it's from a transactional datasource. If this is not enough information let me know. > jpa JTA transaction and missing jta-data-source should be warned about or rejected > ---------------------------------------------------------------------------------- > > Key: GERONIMO-5824 > URL: https://issues.apache.org/jira/browse/GERONIMO-5824 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence > Affects Versions: 2.1.8, 2.2.2, 3.0 > Reporter: David Jencks > > Someone just had a lot of weird transaction errors that turned out to be because they had configured a persistence.xml with JTA transaction support and only a non-jta-datasource that was actually transactional. When both the tm and openjpa tried to control the tx confusion enused. > We can detect this situation on deployment and either reject it or at least loudly warn about it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira