[
https://issues.apache.org/jira/browse/HADOOP-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899505#action_12899505
]
Richard Lackey commented on HADOOP-6914:
----------------------------------------
It appears to be a duplicate.
The proposed fix is different. The patch insures that close does not percolate
a RuntimeException, and checks the socket and associated streams streams. This
appears to be more inline with the implied contract for Client.close().
> IPC Client Connection close does not protect against partially Connection
> objects
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6914
> URL: https://issues.apache.org/jira/browse/HADOOP-6914
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.20.0
> Reporter: Richard Lackey
> Attachments: hbase-2042.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> The purpose of this ticket is to cross-reference hbase-2042, opened
> 12/12/2009. close() is used to release Connection resources. It is invoked
> even though the Connection object may not have been completely initialized.
> For example, the file descriptor ulimit may have been exceeded in which case
> no socket would have been acquired. The result would be an NPE in close. The
> implied contract for close() seems to be that it will never fail.
> There is a proposed patch in the hbase-2042 ticket.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
