You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2017/02/28 22:34:45 UTC

[jira] [Closed] (YOKO-467) Fix a bunch of deadlocks by using executor services instead of thread groups

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

David Jencks closed YOKO-467.
-----------------------------
    Resolution: Fixed

> 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.15#6346)