geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <j...@apache.org>
Subject [jira] Created: (YOKO-424) Yoko default concurrency model different from other orb implementations.
Date Wed, 26 Mar 2008 11:47:24 GMT
Yoko default concurrency model different from other orb implementations.
------------------------------------------------------------------------

                 Key: YOKO-424
                 URL: https://issues.apache.org/jira/browse/YOKO-424
             Project: Yoko - CORBA Server
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: orb core
    Affects Versions: v1.0.0
            Reporter: Rick McGuire
            Assignee: Rick McGuire
             Fix For: v1.0.0


The yoko default concurrency model is "thread_per_client", which uses a single thread for
all requests coming from a client application.  This can lead to deadlock situations with
applications that have been ported from other ORBs because additional requests from a client
get queued up behind the currently active request.  This situation is EXTREMELY difficult
to diagnose, since the application will just hang without any diagnostics on the situation.
 Neither the Sun ORB or the IBM ORB display this behavior, so the safer default concurrency
model would be to use a thread pool to dispatch requests.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message