[
https://issues.apache.org/jira/browse/HAMA-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174477#comment-13174477
]
Hudson commented on HAMA-489:
-----------------------------
Integrated in Hama-Nightly #402 (See
[https://builds.apache.org/job/Hama-Nightly/402/])
[HAMA-489] Check port availability before forking child process
edwardyoon :
Files :
* /incubator/hama/trunk/CHANGES.txt
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/GroomServer.java
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/util/BSPNetUtils.java
> Check port availability before forking child process
> ----------------------------------------------------
>
> Key: HAMA-489
> URL: https://issues.apache.org/jira/browse/HAMA-489
> Project: Hama
> Issue Type: Bug
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.4.0
>
> Attachments: HAMA-489.patch
>
>
> {code}
> for (GroomServerAction action : actions) {
> Task t = ((LaunchTaskAction) action).getTask();
> int peerPort = (Constants.DEFAULT_PEER_PORT + i);
> assignedPeerNames.put(t.getTaskID(), peerPort);
> i++;
> }
> {code}
> Increasing naively the number of port will potentially cause "already in use"
> error. We may need to find next available port.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
