[
https://issues.apache.org/jira/browse/THRIFT-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Duxbury updated THRIFT-73:
--------------------------------
Attachment: thrift-73-v2.patch
Here's a version with a teensy comment about flow.
Commit message:
THRIFT-73: java: fixed a bug where TNonblockingServer (and by extension
THsHaServer) could permanently lose track of client connections if the message
on-wire was malformed. If the client sends a bad message now, the server will
close the transport at its earliest convenience.
> TNonblockingServer loses client sockets permanently if wire data is corrupt
> ---------------------------------------------------------------------------
>
> Key: THRIFT-73
> URL: https://issues.apache.org/jira/browse/THRIFT-73
> Project: Thrift
> Issue Type: Bug
> Components: Library (Java)
> Reporter: Bryan Duxbury
> Assignee: Bryan Duxbury
> Attachments: thrift-73-v2.patch, thrift-73.patch
>
>
> We currently have a problem where some bad messages are getting sent through
> to one of our servers. It results in an unhandled exception in
> FrameBuffer.invoke, which kills the worker thread but fails to close that
> socket. The result is a hung client, perpetually waiting for the server to
> start writing.
> The server should be resilient to such message corruption issues and close
> the client socket.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
