You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/03/06 21:19:33 UTC

[jira] [Commented] (ARIES-1689) JpaInterceptor is not thread safe

    [ https://issues.apache.org/jira/browse/ARIES-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898125#comment-15898125 ] 

ASF subversion and git services commented on ARIES-1689:
--------------------------------------------------------

Commit 1785768 from [~ggerla] in branch 'aries/trunk'
[ https://svn.apache.org/r1785768 ]

[ARIES-1689] added test to reproduce the problem

> 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.6.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)