[
https://issues.apache.org/jira/browse/ARIES-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated ARIES-1689:
---------------------------------------
Comment: was deleted
(was: I think an AtomicBoolean for the check is the safest bet. It should also
be as fast as the other solutions.)
> JpaInterceptor is not thread safe
> ---------------------------------
>
> Key: ARIES-1689
> URL: https://issues.apache.org/jira/browse/ARIES-1689
> Project: Aries
> Issue Type: Bug
> Components: JPA
> Affects Versions: jpa-2.4.0, jpa-2.5.0
> Reporter: Giuseppe Gerla
> Assignee: Giuseppe Gerla
> Fix For: jpa-2.7.0
>
>
> If two thread try to access to JpaInterceptor could happen that first thread
> set the value of coordinator but not yet the em. The second one found the
> coordinator setted and try to access to em.
> NullPointerException is raised
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
