You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michael K. Edwards (JIRA)" <ji...@apache.org> on 2018/11/22 21:58:00 UTC
[jira] [Created] (ZOOKEEPER-3198) Handle port-binding failures in a
systematic and documented fashion
Michael K. Edwards created ZOOKEEPER-3198:
---------------------------------------------
Summary: 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.4.13, 3.5.3, 3.6.0
Reporter: Michael K. Edwards
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)