You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Galen O'Sullivan (JIRA)" <ji...@apache.org> on 2017/09/22 20:43:00 UTC

[jira] [Resolved] (GEODE-3080) Protocol connection runs in selector thread

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

Galen O'Sullivan resolved GEODE-3080.
-------------------------------------
       Resolution: Fixed
         Assignee: Galen O'Sullivan
    Fix Version/s: 1.3.0

> Protocol connection runs in selector thread
> -------------------------------------------
>
>                 Key: GEODE-3080
>                 URL: https://issues.apache.org/jira/browse/GEODE-3080
>             Project: Geode
>          Issue Type: Sub-task
>          Components: client/server
>            Reporter: Galen O'Sullivan
>            Assignee: Galen O'Sullivan
>             Fix For: 1.3.0
>
>
> As a user of the new protocol, I need it to function whether or not I explicitly set max connections.
> Ensure Path #2 is functional -- {{isSelector}} is true.
> Make {{NewClientServerConnection}} able to run when its acceptor {{isSelector()}}. This means checking {{isSelector()}} in the run() method and handling a single message and returning, rather than running a long-running thread loop.
> (Path 1 -- isSelector() is false -- is covered in GEODE-3078.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)