[
https://issues.apache.org/jira/browse/AIRAVATA-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie updated AIRAVATA-2961:
--------------------------------------
Description:
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.
was: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.
> 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)
