airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AIRAVATA-2961) Thread-safe getEntityManager
Date Wed, 06 Feb 2019 18:19:00 GMT

     [ https://issues.apache.org/jira/browse/AIRAVATA-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcus Christie resolved AIRAVATA-2961.
---------------------------------------
    Resolution: Fixed

Removing local reference to EntityManager fixes the thread-safety issue since EntityManagerFactory
is already thread safe

> Thread-safe getEntityManager
> ----------------------------
>
>                 Key: AIRAVATA-2961
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2961
>             Project: Airavata
>          Issue Type: Bug
>            Reporter: Marcus Christie
>            Priority: Major
>
> Something similar to what was done for the app catalog in the old registry (see [this
commit|https://github.com/apache/airavata/commit/f51f1f16ff687768f7cfade2b92e66b84bd105d8?w=1])
should be done for the new registry EntityManager utilities.
> I'm also wondering if we really need to evict the cache. Since gfac is calling the registry
through the CPI this shouldn't be needed. Or we should just disable second level cache.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message