Uploaded image for project: 'TinkerPop'
  1. TinkerPop
  2. TINKERPOP-816

Gryo deserialization of error response with null message causes NPE and protocol desync

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            spmallette Stephen Mallette
            gereedy Geoff Reedy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment