[
https://issues.apache.org/jira/browse/PHOENIX-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677466#comment-16677466
]
Hudson commented on PHOENIX-5004:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-omid2 #143 (See
[https://builds.apache.org/job/Phoenix-omid2/143/])
PHOENIX-5004 Fix org.jboss.netty.channel.ChannelException: Failed to
(jamestaylor: rev e13de05a252a8aaaaeb56e1292225199cdefb81c)
* (edit)
phoenix-core/src/test/java/org/apache/phoenix/query/QueryServicesTestImpl.java
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexToolIT.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/transaction/OmidTransactionProvider.java
> Fix org.jboss.netty.channel.ChannelException: Failed to bind to: flapper
> ------------------------------------------------------------------------
>
> Key: PHOENIX-5004
> URL: https://issues.apache.org/jira/browse/PHOENIX-5004
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Yonatan Gottesman
> Priority: Major
>
> Recent Jenkins runs on omid2 are flapping with the following exception:
> {code:java}
> com.google.common.util.concurrent.UncheckedExecutionException:
> org.jboss.netty.channel.ChannelException: Failed to bind to:
> 0.0.0.0/0.0.0.0:41016
> at
> org.apache.phoenix.end2end.IndexToolIT.testSecondaryIndex(IndexToolIT.java:150)
> {code}
> See [https://builds.apache.org/job/Phoenix-omid2/141/]
> Do you think we might be running into OOM errors given that the tso needs so
> much memory? Maybe we need to increase our heapsize when the the tests are
> run? Other ideas?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
