Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Date: Mon, 18 May 2015 09:44:00 +0000 (UTC)
From: "Hannes Bjurek (JIRA)" <jira@apache.org>
To: dev@aries.apache.org
Message-ID: <JIRA.12600321.1343310325000.142413.1431942240114@Atlassian.JIRA>
In-Reply-To: <JIRA.12600321.1343310325000@Atlassian.JIRA>
References: <JIRA.12600321.1343310325000@Atlassian.JIRA>
 <JIRA.12600321.1343310325603@arcas>
Subject: [jira] [Commented] (ARIES-885) In container managed mode, a single
 non thread safe entity manager is used to service all requests when no
 transaction is active
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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)