Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Wed, 29 Jul 2015 18:49:05 +0000 (UTC)
From: "Christian Schneider (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <JIRA.12849904.1438169027000.322577.1438195745627@Atlassian.JIRA>
In-Reply-To: <JIRA.12849904.1438169027000@Atlassian.JIRA>
References: <JIRA.12849904.1438169027000@Atlassian.JIRA>
 <JIRA.12849904.1438169027681@arcas>
Subject: [jira] [Commented] (FELIX-4976) Coordinations are always ORPHANED
 if they only are on the thread stack
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FELIX-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646599#comment-14646599 ] 

Christian Schneider commented on FELIX-4976:
--------------------------------------------

Tested my fix with Aries transaction and Aries jpa. All tests now work without the workaround. 

> Coordinations are always ORPHANED if they only are on the thread stack
> ----------------------------------------------------------------------
>
>                 Key: FELIX-4976
>                 URL: https://issues.apache.org/jira/browse/FELIX-4976
>             Project: Felix
>          Issue Type: Bug
>          Components: Coordinator Service
>    Affects Versions: coordinator-1.0.0
>            Reporter: Christian Schneider
>            Priority: Critical
>             Fix For: coordinator-1.0.2
>
>
> The calls below should work but failed as the coordination is regarded as ORPHANED.
> coordinator.begin("test", 0);
> System.gc();
> coordinator.pop().end();
> I can try to provide a fix if you want.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)