[
https://issues.apache.org/jira/browse/TINKERPOP-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Mallette closed TINKERPOP-2410.
---------------------------------------
Resolution: Fixed
just reopened to add fix version and assignee - closed
> Free up server threads when client is closed
> --------------------------------------------
>
> Key: TINKERPOP-2410
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2410
> Project: TinkerPop
> Issue Type: Bug
> Components: server
> Affects Versions: 3.4.8
> Reporter: Divij Vaidya
> Assignee: Divij Vaidya
> Priority: Minor
> Fix For: 3.5.0, 3.4.9
>
>
> Consider a situation where the server has sent some results back to the
> client and is waiting for Netty channel to be writable again before sending
> rest of the results. Let's assume that the client dies (or is closed) at this
> instant without consuming the entire set of results.
> In this case, the server threads will continue to wait for the channel to
> become writable (which it never will since client is dead) until the timeout
> is hit.
> We need to change the behaviour such that the waiting thread loop breaks if
> the channel becomes inactive. Such loop exists at TraversalOpProcessor (for
> bytecode execution) and AbstractOpProcessor(for string execution) in the
> server.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
