[THRIFT-5083] NetStd JSON Protocol left in incorrect state

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 0.14.0
• Component/s: netstd - Library
• Assignee: Paulo Neves
• Reporter: Paulo Neves
• Created: 05/Feb/20 10:48
• Updated: 11/Feb/21 22:27
• Resolved: 05/Feb/20 20:43

Description

This is the exact same problem as #3743.

When a message writeEnd or readBegin are called the context is not cleaned leading to possible undefined state of the context.

The error was visible for me when i would make 2 RPC calls with the same protocol instance, producing invalid messages like [<message1>],[<message2>]. The comma is a syntax error and invalid JSON and protocol.

Resetting the context as is done for java fixes the issue.

Issue Links

• links to: GitHub Pull Request #2001