Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Thu, 30 Jul 2015 21:26:04 +0000 (UTC)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: <JIRA.12850415.1438291520000.334617.1438291564672@Atlassian.JIRA>
In-Reply-To: <JIRA.12850415.1438291520000@Atlassian.JIRA>
References: <JIRA.12850415.1438291520000@Atlassian.JIRA>
 <JIRA.12850415.1438291520905@arcas>
Subject: [jira] [Created] (YOKO-467) Fix a bunch of deadlocks by using
 executor services instead of thread groups
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

David Jencks created YOKO-467:
---------------------------------

             Summary: Fix a bunch of deadlocks by using executor services instead of thread groups
                 Key: YOKO-467
                 URL: https://issues.apache.org/jira/browse/YOKO-467
             Project: Yoko - CORBA Server
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: orb core
    Affects Versions: v1.1.0
            Reporter: David Jencks
            Assignee: David Jencks


Yoko internal thread usage relies on thread groups and some jdk-implementation specific assumptions about notifications to detect thread shutdown. These assumptions are false on (at least) ibm jdks.  Use of Executors is a lot clearer and avoids these deadlocks, as well as promoting thread reuse.


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