Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1968722553.332301266403888197.JavaMail.jira@brutus.apache.org>
Date: Wed, 17 Feb 2010 10:51:28 +0000 (UTC)
From: "Alexandros Karypidis (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-4552) Allow application to manipulate the
 transaction state while NOT inside a distributed transaction
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Allow application to manipulate the transaction state while NOT inside a distributed transaction
------------------------------------------------------------------------------------------------

                 Key: DERBY-4552
                 URL: https://issues.apache.org/jira/browse/DERBY-4552
             Project: Derby
          Issue Type: Bug
          Components: JDBC
    Affects Versions: 10.4.2.0
         Environment: Geronimo 2.2 with Jetty, OpenJPA 1.2.1 & Derby 10.4.2.0
            Reporter: Alexandros Karypidis


Enhancement http://issues.apache.org/jira/browse/DERBY-1236 prevents applications from modifying the transaction state when using a global transaction. However, an application may access Derby using the XA adapter and issue statements without a global transaction being active. In that case, the auto-commit should be allowed.

This issue is revealed when trying to use the schema-generation facility of OpenJPA. I contacted the OpenJPA folks and you can see the details in this thread: http://n2.nabble.com/Schema-generation-uses-auto-commit-mode-breaks-on-XA-data-sources-tp4583095p4583095.html


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.