[GitHub] [tinkerpop] spmallette opened pull request #1047: TINKERPOP-2139 Properly handle client side serialization exceptions

["spmallette (GitHub)" <gi...@apache.org>]

https://issues.apache.org/jira/browse/TINKERPOP-2139

Prior to this change serialization exceptions were basically just logged because any failure would signal a bad host and mark it as dead, but that's not really what was happening obviously if the client was never even able to try to send the message to the host in the first place. These sorts of client exceptions are now handled better and actually throw an exception that the calling client can see and utilize while not killing the host.

All tests pass with `docker/build.sh -t -n -i`

VOTE +1

[ Full content available at: https://github.com/apache/tinkerpop/pull/1047 ]
This message was relayed via gitbox.apache.org for dev@tinkerpop.apache.org

[GitHub] [tinkerpop] spmallette closed pull request #1047: TINKERPOP-2139 Properly handle client side serialization exceptions

["spmallette (GitHub)" <gi...@apache.org>]

[ pull request closed by spmallette ]

[ Full content available at: https://github.com/apache/tinkerpop/pull/1047 ]
This message was relayed via gitbox.apache.org for dev@tinkerpop.apache.org

[GitHub] [tinkerpop] dkuppitz commented on issue #1047: TINKERPOP-2139 Properly handle client side serialization exceptions

["dkuppitz (GitHub)" <gi...@apache.org>]

VOTE +1

[ Full content available at: https://github.com/apache/tinkerpop/pull/1047 ]
This message was relayed via gitbox.apache.org for dev@tinkerpop.apache.org

[GitHub] [tinkerpop] nastra commented on issue #1047: TINKERPOP-2139 Properly handle client side serialization exceptions

["nastra (GitHub)" <gi...@apache.org>]

VOTE +1

[ Full content available at: https://github.com/apache/tinkerpop/pull/1047 ]
This message was relayed via gitbox.apache.org for dev@tinkerpop.apache.org