You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Ryan Heinen (JIRA)" <ji...@apache.org> on 2014/10/01 02:26:33 UTC

[jira] [Created] (OPENJPA-2532) JDBC connection transaction/autocommit state is not restored when connections are closed

Ryan Heinen created OPENJPA-2532:
------------------------------------

             Summary: JDBC connection transaction/autocommit state is not restored when connections are closed
                 Key: OPENJPA-2532
                 URL: https://issues.apache.org/jira/browse/OPENJPA-2532
             Project: OpenJPA
          Issue Type: Bug
          Components: jdbc
    Affects Versions: 2.3.0
            Reporter: Ryan Heinen


OpenJPA does not restore the autocommit property to it's original state before closing a connection, nor does it roll back or commit in-flight transactions.

In JDBCStoreManager.begin() OpenJPA sets autocommit to true, but when closing the connection later in close() it simply delegates to Connection.close().

This can create a problem with connection pools that do not automatically restore these settings when connections are returned, but instead rely on the client to clean up, for example tomcat-pool.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)