[
https://issues.apache.org/jira/browse/ARIES-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547781#comment-14547781
]
Hannes Bjurek commented on ARIES-885:
-------------------------------------
This code is not working for us. When deploying multiple bundles that contains
a Meta-Persistence in the MANIFEST some of the bundles get:
2015-05-18 11:20:42,661 | ERROR | /author/services | | |
a.blueprint.aries.impl.NSHandler 163 | 73 -
org.apache.aries.jpa.blueprint.aries - 1.0.5.SNAPSHOT | No
org.apache.aries.jpa.container.sync.Synchronization service registered.
When restarting the error will be shuffled around to other services. I get the
same error on 1.0.4
It seems to be some kind of race between the addingService and the
registerContext inside PersistenceContextManager. When failing, the registerEM
never gets called.
> In container managed mode, a single non thread safe entity manager is used to
> service all requests when no transaction is active
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-885
> URL: https://issues.apache.org/jira/browse/ARIES-885
> Project: Aries
> Issue Type: Bug
> Components: JPA
> Affects Versions: 1.0
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: jpa-container-context-1.0.3
>
>
> The EntityManager object is not thread safe, so the access to the shared
> entity manager should be synchronized.
> This could eventually be made optional, but the default should be to be
> synchronized to avoid problems, disabling the synchronization should be an
> optional setting depending on which JPA provider is used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
