You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "Bob Briody (JIRA)" <ji...@apache.org> on 2015/12/16 21:02:46 UTC

[jira] [Commented] (TINKERPOP-956) Connection errors tend to force a complete close of the channel

    [ https://issues.apache.org/jira/browse/TINKERPOP-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060722#comment-15060722 ] 

Bob Briody commented on TINKERPOP-956:
--------------------------------------

So far I have seen 2 things trigger this:
- Executing a lambda against a "no-lamdas-allowed" graph.
- Attempt to serialize classes that are not handled.

> 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.1-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)