[
https://issues.apache.org/jira/browse/ARIES-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126756#comment-14126756
]
Torsten Mielke commented on ARIES-885:
--------------------------------------
I tested the jpa20 backport today using different databases (MySQL, Microsoft
SQL Server 2008) and drivers (jtds, Microsoft's sqljdbc4.jar and MySQL driver)
and found the problem fixed.
Before the fix I would get ConcurrentModificationExceptions and low level JDBC
driver exceptions when calling a JPA bean concurrently, now these exceptions
are all gone.
> In container managed mode, a single non thread safe entity manager is used to
> service all requests when no transaction is active
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-885
> URL: https://issues.apache.org/jira/browse/ARIES-885
> Project: Aries
> Issue Type: Bug
> Components: JPA
> Affects Versions: 1.0
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: jpa-container-context-1.0.3
>
>
> The EntityManager object is not thread safe, so the access to the shared
> entity manager should be synchronized.
> This could eventually be made optional, but the default should be to be
> synchronized to avoid problems, disabling the synchronization should be an
> optional setting depending on which JPA provider is used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
