[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=15898775#comment-15898775 ] ASF subversion and git services commented on ARIES-1689: Commit 1785796 from [~ch...@die-schneider.net] in branch 'aries/trunk' [ https://svn.apache.org/r1785796 ] Revert "[ARIES-1689] Fix initialization" This was broken. Reverting to Guiseppes solution. > 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)
[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=15898196#comment-15898196 ] Christian Schneider commented on ARIES-1689: 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)
[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=15898194#comment-15898194 ] ASF subversion and git services commented on ARIES-1689: Commit 1785770 from [~ch...@die-schneider.net] in branch 'aries/trunk' [ https://svn.apache.org/r1785770 ] [ARIES-1689] Fix initialization > 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)
[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=15898128#comment-15898128 ] ASF subversion and git services commented on ARIES-1689: Commit 1785769 from [~ggerla] in branch 'aries/trunk' [ https://svn.apache.org/r1785769 ] [ARIES-1689] Added check that entity manager is not null > 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)
[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=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)
[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=15875730#comment-15875730 ] ASF subversion and git services commented on ARIES-1689: Commit 1783861 from [~ch...@die-schneider.net] in branch 'aries/trunk' [ https://svn.apache.org/r1783861 ] [ARIES-1689] Improve performance > 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)
