[jira] [Updated] (HADOOP-6722) NetUtils.connect should check that it hasn't connected a socket to itself

[ https://issues.apache.org/jira/browse/HADOOP-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HADOOP-6722: Fix Version/s: 0.20.205.0 > NetUtils.connect should check that it hasn't connected a socke

[jira] [Updated] (HADOOP-6722) NetUtils.connect should check that it hasn't connected a socket to itself

[ https://issues.apache.org/jira/browse/HADOOP-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HADOOP-6722: Attachment: HADOOP-6722.20s.patch Patch for 0.20-security. > NetUtils.connect should chec

[jira] Updated: (HADOOP-6722) NetUtils.connect should check that it hasn't connected a socket to itself

[ https://issues.apache.org/jira/browse/HADOOP-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom White updated HADOOP-6722: -- Status: Resolved (was: Patch Available) Hadoop Flags: [Reviewed] Fix Version/s: 0.22.0

[jira] Updated: (HADOOP-6722) NetUtils.connect should check that it hasn't connected a socket to itself

[ https://issues.apache.org/jira/browse/HADOOP-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HADOOP-6722: Status: Patch Available (was: Open) > NetUtils.connect should check that it hasn't connected a so

[jira] Updated: (HADOOP-6722) NetUtils.connect should check that it hasn't connected a socket to itself

[ https://issues.apache.org/jira/browse/HADOOP-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HADOOP-6722: Attachment: hadoop-6722.txt Here's a patch which detects this situation and throws a ConnectExcept