[
https://issues.apache.org/jira/browse/HADOOP-6528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856423#action_12856423
]
Greg Wilkins commented on HADOOP-6528:
--------------------------------------
I'm still pondering this one... and still can't think of an explanation other
than something in hadoop is calling close.
I've attached a patch to http://jira.codehaus.org/browse/JETTY-748 that changes
the way localPort is handled:
Instead of calling socket.getLocalPort() when connector.getLocalPort() is
called, this patch calls socket.getLocalPort() in the open method and holds the
result in a volatile int. If close is called, the int is set to -2, so this
will tell us if the port has not been opened, or has been closed before it was
used.
This patch is not yet in a release, but if somebody has a setup where this
problem occurs, then we can produce a snapshot build for you to test against.
> Jetty returns -1 resulting in Hadoop masters / slaves to fail during startup.
> -----------------------------------------------------------------------------
>
> Key: HADOOP-6528
> URL: https://issues.apache.org/jira/browse/HADOOP-6528
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Hemanth Yamijala
> Attachments: jetty-server-failure.log
>
>
> A recent test failure on Hudson seems to indicate that Jetty's
> Server.getConnectors()[0].getLocalPort() is returning -1 in the
> HttpServer.getPort() method. When this happens, Hadoop masters / slaves that
> use Jetty fail to startup correctly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
