[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14904354#comment-14904354 ] Bibin A Chundatt commented on YARN-3433: Hi [~ste...@apache.org] The same failed with port in use again during one of ci build https://builds.apache.org/job/PreCommit-YARN-Build/9232/testReport > Jersey tests failing with Port in Use -again > > > Key: YARN-3433 > URL: https://issues.apache.org/jira/browse/YARN-3433 > Project: Hadoop YARN > Issue Type: Bug > Components: build, test >Affects Versions: 3.0.0 > Environment: ASF Jenkins >Reporter: Steve Loughran >Assignee: Brahma Reddy Battula >Priority: Critical > Fix For: 2.8.0 > > Attachments: YARN-3433.patch > > > ASF Jenkins jersey tests failing with port in use exceptions. > The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't > scan for a spare port —so is too brittle on a busy server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747227#comment-14747227 ] Hudson commented on YARN-3433: -- FAILURE: Integrated in Hadoop-trunk-Commit #8465 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8465/]) YARN-3433. Jersey tests failing with Port in Use -again. (Brahma Reddy Battula) (stevel: rev bf2f2b4fc436ea5990e6fc78eb18091b9458e75a) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/webapp/JerseyTestBase.java > Jersey tests failing with Port in Use -again > > > Key: YARN-3433 > URL: https://issues.apache.org/jira/browse/YARN-3433 > Project: Hadoop YARN > Issue Type: Bug > Components: build, test >Affects Versions: 3.0.0 > Environment: ASF Jenkins >Reporter: Steve Loughran >Assignee: Brahma Reddy Battula >Priority: Critical > Fix For: 2.8.0 > > Attachments: YARN-3433.patch > > > ASF Jenkins jersey tests failing with port in use exceptions. > The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't > scan for a spare port —so is too brittle on a busy server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14768846#comment-14768846 ] Hudson commented on YARN-3433: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #396 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/396/]) YARN-3433. Jersey tests failing with Port in Use -again. (Brahma Reddy Battula) (stevel: rev bf2f2b4fc436ea5990e6fc78eb18091b9458e75a) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/webapp/JerseyTestBase.java * hadoop-yarn-project/CHANGES.txt > Jersey tests failing with Port in Use -again > > > Key: YARN-3433 > URL: https://issues.apache.org/jira/browse/YARN-3433 > Project: Hadoop YARN > Issue Type: Bug > Components: build, test >Affects Versions: 3.0.0 > Environment: ASF Jenkins >Reporter: Steve Loughran >Assignee: Brahma Reddy Battula >Priority: Critical > Fix For: 2.8.0 > > Attachments: YARN-3433.patch > > > ASF Jenkins jersey tests failing with port in use exceptions. > The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't > scan for a spare port —so is too brittle on a busy server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14768859#comment-14768859 ] Hudson commented on YARN-3433: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #379 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/379/]) YARN-3433. Jersey tests failing with Port in Use -again. (Brahma Reddy Battula) (stevel: rev bf2f2b4fc436ea5990e6fc78eb18091b9458e75a) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/webapp/JerseyTestBase.java * hadoop-yarn-project/CHANGES.txt > Jersey tests failing with Port in Use -again > > > Key: YARN-3433 > URL: https://issues.apache.org/jira/browse/YARN-3433 > Project: Hadoop YARN > Issue Type: Bug > Components: build, test >Affects Versions: 3.0.0 > Environment: ASF Jenkins >Reporter: Steve Loughran >Assignee: Brahma Reddy Battula >Priority: Critical > Fix For: 2.8.0 > > Attachments: YARN-3433.patch > > > ASF Jenkins jersey tests failing with port in use exceptions. > The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't > scan for a spare port —so is too brittle on a busy server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747347#comment-14747347 ] Hudson commented on YARN-3433: -- FAILURE: Integrated in Hadoop-Yarn-trunk #1137 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/1137/]) YARN-3433. Jersey tests failing with Port in Use -again. (Brahma Reddy Battula) (stevel: rev bf2f2b4fc436ea5990e6fc78eb18091b9458e75a) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/webapp/JerseyTestBase.java * hadoop-yarn-project/CHANGES.txt > Jersey tests failing with Port in Use -again > > > Key: YARN-3433 > URL: https://issues.apache.org/jira/browse/YARN-3433 > Project: Hadoop YARN > Issue Type: Bug > Components: build, test >Affects Versions: 3.0.0 > Environment: ASF Jenkins >Reporter: Steve Loughran >Assignee: Brahma Reddy Battula >Priority: Critical > Fix For: 2.8.0 > > Attachments: YARN-3433.patch > > > ASF Jenkins jersey tests failing with port in use exceptions. > The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't > scan for a spare port —so is too brittle on a busy server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747353#comment-14747353 ] Brahma Reddy Battula commented on YARN-3433: [~ste...@apache.org] thanks for committing!! > Jersey tests failing with Port in Use -again > > > Key: YARN-3433 > URL: https://issues.apache.org/jira/browse/YARN-3433 > Project: Hadoop YARN > Issue Type: Bug > Components: build, test >Affects Versions: 3.0.0 > Environment: ASF Jenkins >Reporter: Steve Loughran >Assignee: Brahma Reddy Battula >Priority: Critical > Fix For: 2.8.0 > > Attachments: YARN-3433.patch > > > ASF Jenkins jersey tests failing with port in use exceptions. > The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't > scan for a spare port —so is too brittle on a busy server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747313#comment-14747313 ] Hudson commented on YARN-3433: -- SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #403 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/403/]) YARN-3433. Jersey tests failing with Port in Use -again. (Brahma Reddy Battula) (stevel: rev bf2f2b4fc436ea5990e6fc78eb18091b9458e75a) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/webapp/JerseyTestBase.java > Jersey tests failing with Port in Use -again > > > Key: YARN-3433 > URL: https://issues.apache.org/jira/browse/YARN-3433 > Project: Hadoop YARN > Issue Type: Bug > Components: build, test >Affects Versions: 3.0.0 > Environment: ASF Jenkins >Reporter: Steve Loughran >Assignee: Brahma Reddy Battula >Priority: Critical > Fix For: 2.8.0 > > Attachments: YARN-3433.patch > > > ASF Jenkins jersey tests failing with port in use exceptions. > The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't > scan for a spare port —so is too brittle on a busy server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747359#comment-14747359 ] Hudson commented on YARN-3433: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2343 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2343/]) YARN-3433. Jersey tests failing with Port in Use -again. (Brahma Reddy Battula) (stevel: rev bf2f2b4fc436ea5990e6fc78eb18091b9458e75a) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/webapp/JerseyTestBase.java > Jersey tests failing with Port in Use -again > > > Key: YARN-3433 > URL: https://issues.apache.org/jira/browse/YARN-3433 > Project: Hadoop YARN > Issue Type: Bug > Components: build, test >Affects Versions: 3.0.0 > Environment: ASF Jenkins >Reporter: Steve Loughran >Assignee: Brahma Reddy Battula >Priority: Critical > Fix For: 2.8.0 > > Attachments: YARN-3433.patch > > > ASF Jenkins jersey tests failing with port in use exceptions. > The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't > scan for a spare port —so is too brittle on a busy server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790533#comment-14790533 ] Hudson commented on YARN-3433: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2319 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2319/]) YARN-3433. Jersey tests failing with Port in Use -again. (Brahma Reddy Battula) (stevel: rev bf2f2b4fc436ea5990e6fc78eb18091b9458e75a) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/webapp/JerseyTestBase.java * hadoop-yarn-project/CHANGES.txt > Jersey tests failing with Port in Use -again > > > Key: YARN-3433 > URL: https://issues.apache.org/jira/browse/YARN-3433 > Project: Hadoop YARN > Issue Type: Bug > Components: build, test >Affects Versions: 3.0.0 > Environment: ASF Jenkins >Reporter: Steve Loughran >Assignee: Brahma Reddy Battula >Priority: Critical > Fix For: 2.8.0 > > Attachments: YARN-3433.patch > > > ASF Jenkins jersey tests failing with port in use exceptions. > The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't > scan for a spare port —so is too brittle on a busy server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14745870#comment-14745870 ] Brahma Reddy Battula commented on YARN-3433: Makrking as critical,recent pre-commit build has failing because address already in use.. https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2336/ > Jersey tests failing with Port in Use -again > > > Key: YARN-3433 > URL: https://issues.apache.org/jira/browse/YARN-3433 > Project: Hadoop YARN > Issue Type: Bug > Components: build, test >Affects Versions: 3.0.0 > Environment: ASF Jenkins >Reporter: Steve Loughran >Assignee: Brahma Reddy Battula >Priority: Critical > Attachments: YARN-3433.patch > > > ASF Jenkins jersey tests failing with port in use exceptions. > The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't > scan for a spare port —so is too brittle on a busy server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732329#comment-14732329 ] Brahma Reddy Battula commented on YARN-3433: Attached the patch.. Kindly Review.. > Jersey tests failing with Port in Use -again > > > Key: YARN-3433 > URL: https://issues.apache.org/jira/browse/YARN-3433 > Project: Hadoop YARN > Issue Type: Bug > Components: build, test >Affects Versions: 3.0.0 > Environment: ASF Jenkins >Reporter: Steve Loughran >Assignee: Brahma Reddy Battula > Attachments: YARN-3433.patch > > > ASF Jenkins jersey tests failing with port in use exceptions. > The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't > scan for a spare port —so is too brittle on a busy server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[
https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732338#comment-14732338
]
Hadoop QA commented on YARN-3433:
-
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | pre-patch | 5m 46s | Findbugs (version ) appears to
be broken on trunk. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:green}+1{color} | tests included | 0m 0s | The patch appears to
include 1 new or modified test files. |
| {color:green}+1{color} | javac | 7m 41s | There were no new javac warning
messages. |
| {color:green}+1{color} | release audit | 0m 20s | The applied patch does
not increase the total number of release audit warnings. |
| {color:green}+1{color} | checkstyle | 0m 28s | There were no new checkstyle
issues. |
| {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that
end in whitespace. |
| {color:green}+1{color} | install | 1m 26s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 32s | The patch built with
eclipse:eclipse. |
| {color:green}+1{color} | findbugs | 1m 32s | The patch does not introduce
any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | yarn tests | 1m 57s | Tests passed in
hadoop-yarn-common. |
| | | 19m 45s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12754383/YARN-3433.patch |
| Optional Tests | javac unit findbugs checkstyle |
| git revision | trunk / 9b68577 |
| hadoop-yarn-common test log |
https://builds.apache.org/job/PreCommit-YARN-Build/9017/artifact/patchprocess/testrun_hadoop-yarn-common.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-YARN-Build/9017/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf905.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/9017/console |
This message was automatically generated.
> Jersey tests failing with Port in Use -again
>
>
> Key: YARN-3433
> URL: https://issues.apache.org/jira/browse/YARN-3433
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, test
>Affects Versions: 3.0.0
> Environment: ASF Jenkins
>Reporter: Steve Loughran
>Assignee: Brahma Reddy Battula
> Attachments: YARN-3433.patch
>
>
> ASF Jenkins jersey tests failing with port in use exceptions.
> The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't
> scan for a spare port —so is too brittle on a busy server
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again
[
https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392497#comment-14392497
]
Steve Loughran commented on YARN-3433:
--
{code}
com.sun.jersey.test.framework.spi.container.TestContainerException:
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:444)
at sun.nio.ch.Net.bind(Net.java:436)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at
org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:413)
at
org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:384)
at
org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:375)
at
org.glassfish.grizzly.http.server.NetworkListener.start(NetworkListener.java:549)
at
org.glassfish.grizzly.http.server.HttpServer.start(HttpServer.java:255)
at
com.sun.jersey.api.container.grizzly2.GrizzlyServerFactory.createHttpServer(GrizzlyServerFactory.java:326)
at
com.sun.jersey.api.container.grizzly2.GrizzlyServerFactory.createHttpServer(GrizzlyServerFactory.java:343)
at
com.sun.jersey.test.framework.spi.container.grizzly2.web.GrizzlyWebTestContainerFactory$GrizzlyWebTestContainer.instantiateGrizzlyWebServer(GrizzlyWebTestContainerFactory.java:219)
at
com.sun.jersey.test.framework.spi.container.grizzly2.web.GrizzlyWebTestContainerFactory$GrizzlyWebTestContainer.init(GrizzlyWebTestContainerFactory.java:129)
at
com.sun.jersey.test.framework.spi.container.grizzly2.web.GrizzlyWebTestContainerFactory$GrizzlyWebTestContainer.init(GrizzlyWebTestContainerFactory.java:86)
at
com.sun.jersey.test.framework.spi.container.grizzly2.web.GrizzlyWebTestContainerFactory.create(GrizzlyWebTestContainerFactory.java:79)
at
com.sun.jersey.test.framework.JerseyTest.getContainer(JerseyTest.java:342)
at com.sun.jersey.test.framework.JerseyTest.init(JerseyTest.java:217)
at
org.apache.hadoop.yarn.webapp.JerseyTestBase.init(JerseyTestBase.java:27)
at
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesApps.init(TestRMWebServicesApps.java:111)
{code}
Jersey tests failing with Port in Use -again
Key: YARN-3433
URL: https://issues.apache.org/jira/browse/YARN-3433
Project: Hadoop YARN
Issue Type: Bug
Components: test
Affects Versions: 3.0.0
Environment: ASF Jenkins
Reporter: Steve Loughran
ASF Jenkins jersey tests failing with port in use exceptions.
The YARN-2912 patch tried to fix it, but it defaults to port 9998 and doesn't
scan for a spare port —so is too brittle on a busy server
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
