[DERBY-4552] Allow application to manipulate the transaction state while NOT inside a distributed transaction

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.4.2.0
• Component/s: JDBC
• Labels: derby_triage10_8
• Environment: Geronimo 2.2 with Jetty, OpenJPA 1.2.1 & Derby 10.4.2.0
• Urgency: Low
• Bug behavior facts: Deviation from standard, Seen in production
• Assignee: Unassigned
• Reporter: Alexandros Karypidis
• Created: 17/Feb/10 10:49
• Updated: 16/Feb/11 14:39

Description

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

Issue Links

• relates to: DERBY-1236 Verify that applications can't manipulate the transaction state while inside a distributed transaction.