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.
