[
https://issues.apache.org/jira/browse/DEFT-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Schildmeijer updated DEFT-155:
------------------------------------
Description:
If we get an IOException in handleWrite (could be because the connection is
broken/closed) we log, invoke the close callback, closes the channel and
unregister the channel from the ioloop.
BUT then we take the same code path as if it was a successful write.
proposal: add the missing return; statement at the end of the
catch(IOException) clause
(Found while doing DEFT-151 (Distributed demo application (elastica)))
was:
If we get an IOException in handleWrite (could be because the connection is
broken/closed) we log, invoke the close callback, closes the channel and
unregister the channel from the ioloop.
BUT then we take the same code path as if it was a successful write.
proposal: add the missing return; statement at the end of the
catch(IOException) clause
(Found while doing DEFT-150 (Distributed demo application (elastica)))
> NPE in AsynchronousSocket.write
> -------------------------------
>
> Key: DEFT-155
> URL: https://issues.apache.org/jira/browse/DEFT-155
> Project: Deft
> Issue Type: Bug
> Reporter: Roger Schildmeijer
> Assignee: Roger Schildmeijer
> Attachments:
> Implemented+%23DEFT-155+%28NPE+in+AsynchronousSocket.write%29+patch+by+schildmei.patch
>
>
> If we get an IOException in handleWrite (could be because the connection is
> broken/closed) we log, invoke the close callback, closes the channel and
> unregister the channel from the ioloop.
> BUT then we take the same code path as if it was a successful write.
> proposal: add the missing return; statement at the end of the
> catch(IOException) clause
> (Found while doing DEFT-151 (Distributed demo application (elastica)))
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
