openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <>
Subject [jira] [Commented] (OPENJPA-2312) H2 is forced to autoCommit; breaks transactions
Date Wed, 19 Dec 2012 15:39:13 GMT


Kevin Sutter commented on OPENJPA-2312:

It sounds like your usage should not be container-managed connections and transactions.  My
past experiences with Spring and OpenJPA seem to have been centered around container-managed,
but it sounds like your case is more application-managed (or Spring managed).  So, if the
setting of this supportsMultipleNontransactionalResultSets property works for you, that's

I am not an expert with H2, so I don't really know whether the default value for this particular
database should be changed or not.  If more experienced H2 users can vouch for it, then maybe
this default should be changed.  But, for the time being and for this JIRA, I would propose
that the setting in persistence.xml is a suitable solution/workaround.  Agree?

Thanks, Kevin
> H2 is forced to autoCommit; breaks transactions
> -----------------------------------------------
>                 Key: OPENJPA-2312
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Gustavo Lopes
>         Attachments: details.txt
> DataSourceFactory::installDBDictionary() sets autocommit to TRUE on the ConfiguringConnectionDecorator
because supportsMultipleNontransactionalResultSets is true.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message