Strange error in result returned to the client --- Invalid query-Stream closed

[n614cd]

GraphQL Java Version 21.3

Short version: At the end of the response to the client I see the following text: "Invalid query-Stream closed." Otherwise, the respinse is correct, with no missing data. This additional text, then makes the response not valid and of course my app is not able to run. I have searched the code, tried string searching of the binary jar files, I have stepped through the code looking for where this could be appended. I have been unable to find where this is being added. Any suggestions?

Long version: Checking in Chrome and Firefox in the development tabs under the network, I see this text being added to the end of the GraphQL response in the raw response. Running version 21.3 of GraphQL, with the dispatching handled by Netflix DGS. I have made massive changes to my lower level code in Hibernate (replacing a hodge podge of audit approaches with envers), and have changed multiple objects, so it is practically impossible to undo and work backwards to a working version of the system and see when the error was introduced.
I have tried searching for the whole string, parts of the string, searching via grep to include binary files (jars). I have search a downloaded copy of the graphql code. I have the same error, on both audited and unaudited entities. All Hibernate entities are programmatically copied (via reflections) to DTOs after being run through a Hibernate unproxy. Therefore there is no "hibernate" proxies left around to cause the issue (verified in Eclipse debug).
I have enabled the notprivacysafe to debug level, I did not see any errors. What am I missing?

[n614cd]

Never mind. Found it eventually, and yes it was something I did it.
I tracked it down via digging into the Spring and Tomcat response objects looking for when messages are written to the buffer, and back tracing it from there.