[
https://issues.apache.org/jira/browse/OPENJPA-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536043#comment-13536043
]
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 great.
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: https://issues.apache.org/jira/browse/OPENJPA-2312
> 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: http://www.atlassian.com/software/jira
