[
https://issues.apache.org/jira/browse/ZOOKEEPER-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698065#comment-16698065
]
Michael K. Edwards commented on ZOOKEEPER-3198:
-----------------------------------------------
An attempt (as yet, not very successful) to plumb BindExceptions up the stack
is in https://github.com/mkedwards/zookeeper/tree/broken-bind-3.5 . I'm
currently foundering on test cases that call
ReconfigTest.testPortChangeToBlockedPort().
> Handle port-binding failures in a systematic and documented fashion
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-3198
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3198
> Project: ZooKeeper
> Issue Type: Improvement
> Affects Versions: 3.5.3, 3.6.0, 3.4.13
> Reporter: Michael K. Edwards
> Priority: Major
> Fix For: 3.6.0, 3.5.5, 3.4.14
>
>
> Many test failures appear to result from bind failures due to port conflicts.
> This can arise in normal use as well. Presently the code swallows the
> exception (with an error log) at a low level. It would probably be useful to
> throw the exception far enough up the stack to trigger retry with a new port
> (in tests) or a high-level (perhaps even fatal) error message (in normal use).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
