Mailing-List: contact celix-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: celix-dev@incubator.apache.org
Date: Sun, 8 Jun 2014 20:58:01 +0000 (UTC)
From: "Bjoern Petri (JIRA)" <jira@apache.org>
To: celix-commits@incubator.apache.org
Message-ID: <JIRA.12711123.1398761893527.90297.1402261081657@arcas>
In-Reply-To: <JIRA.12711123.1398761893527@arcas>
References: <JIRA.12711123.1398761893527@arcas>
Subject: [jira] [Resolved] (CELIX-114) Potential deadlock in log_service
 bundle during stop
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bjoern Petri resolved CELIX-114.
--------------------------------

    Resolution: Fixed
      Assignee: Bjoern Petri

patch committed for potential deadlock

> Potential deadlock in log_service bundle during stop
> ----------------------------------------------------
>
>                 Key: CELIX-114
>                 URL: https://issues.apache.org/jira/browse/CELIX-114
>             Project: Celix
>          Issue Type: Bug
>            Reporter: Gabriele Ricciardi
>            Assignee: Bjoern Petri
>         Attachments: log_service_deadlock_patch.tgz
>
>
> In a non-sistematic way, the log_service bundle gets stuck during the framework shutdown phase. In particular, after analyzing the core file generated by the application abort, seems that a deadlock condition exists among the removeListener function (blocked on the apr_thread_join) and the logListener thread (waiting on a never-again signalled condition variable).
> Attached a patch solving the issue


--
This message was sent by Atlassian JIRA
(v6.2#6252)