[
https://issues.apache.org/jira/browse/TINKERPOP-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172061#comment-15172061
]
stephen mallette commented on TINKERPOP-956:
--------------------------------------------
I'd venture to say that this is probably one of the few remaining conditions
that force a re-initialization of the driver and it happens in a place that is
somewhat out of the control of my code. standard netty handlers seems to be the
one to close the channel down as a result of this failure. Not sure how to fix
this easily but perhaps impact could be minimized by increasing the default
{{maxContentLength}} for now so that folks don't hit that ceiling too easily.
> Connection errors tend to force a complete close of the channel
> ---------------------------------------------------------------
>
> Key: TINKERPOP-956
> URL: https://issues.apache.org/jira/browse/TINKERPOP-956
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver, server
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Minor
> Fix For: 3.1.2-incubating
>
>
> Would be nice if the channel could stay open if the error is recoverable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
