directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Resolved: (DIR-11) Channel registration in InputManager blocks
Date Thu, 19 Feb 2004 15:04:52 GMT

   The following issue has been resolved as FIXED.

   Resolver: Alex Karasulu
       Date: Thu, 19 Feb 2004 7:03 AM

This was fixed last night by making changes to only capture the ConnectEvent and the DisconnectEvent
for processing later by the selection loop when it wakes up from the select() call.  
View the issue:

Here is an overview of the issue:
        Key: DIR-11
    Summary: Channel registration in InputManager blocks
       Type: Bug

     Status: Resolved
   Priority: Critical
 Resolution: FIXED

    Project: Directory

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Wed, 18 Feb 2004 9:58 AM
    Updated: Thu, 19 Feb 2004 7:03 AM

After a new client is accepted by the ListenerManager a ConnectEvent
is fired on the event router to inform subscribers of the new client socket connection.  The
InputManager is a ConnectEvent subscriber and it needs to be able to register these new channels
with its own
selector to be able to detect incoming IO but within the inform(ConnectEvent) method of the
DefaultInputManager implementation the call to register hangs.  Even with surrounding m_selector.wakeup()
calls I cannot get the code to unblock.  

The code unblocks when the l_channel.configureBlocking( false ) line just above the register()
line is commented out or set to true.  I'm screwing something up here and perhaps it requires
another set of eyes.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message