You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2018/12/17 16:42:00 UTC

[jira] [Resolved] (PHOENIX-5004) Fix org.jboss.netty.channel.ChannelException: Failed to bind to: flapper

     [ https://issues.apache.org/jira/browse/PHOENIX-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor resolved PHOENIX-5004.
-----------------------------------
    Resolution: Fixed

> 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: James Taylor
>            Priority: Major
>             Fix For: 4.15.0
>
>
> 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)