[TINKERPOP-816] Gryo deserialization of error response with null message causes NPE and protocol desync

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.1-incubating
• Fix Version/s: 3.1.0-incubating, 3.0.2-incubating
• Component/s: driver
• Assignee: Stephen Mallette
• Reporter: Geoff Reedy
• Created: 28/Aug/15 14:38
• Updated: 29/Sep/15 20:10
• Resolved: 29/Sep/15 20:10

Description

The issue can be easily reproduced by submitting a query that throws an exception with a null message, e.g.

:> throw new RuntimeException()

This results in a NPE on the client end in GryoMessageSerializerV1d0.dese
rializeResponse

The offending code is the invocation of .intern() on statusMsg on line 208

There are several ways to fix this problem, but I don't see the utility behind interning the message so I suggest removing the call to intern.

Issue Links

• is related to: TINKERPOP-814 ConnectionPool can fill with dead Connections