[
https://issues.apache.org/jira/browse/GEODE-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Baynes updated GEODE-3080:
--------------------------------
Description:
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.)
was: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.
Summary: Protocol connection runs in selector thread (was: Run in
selector thread)
> 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
>
> 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)
