You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <ji...@apache.org> on 2016/06/17 15:00:09 UTC
[jira] [Commented] (DISPATCH-55) Qdrouterd does not exit when
service port is unavailable
[ https://issues.apache.org/jira/browse/DISPATCH-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336256#comment-15336256 ]
Alan Conway commented on DISPATCH-55:
-------------------------------------
I am constantly tripping over this issue - running tests against the wrong router instance or against a broker that is on the same port. It is a pretty bad usability problem.
How about the following:
1. Failure to bind should be *critical*, not just an error. It is disabling the router, it is a critical problem.
2. The default behaviour on failure to bind *during start up* should be to exit with critical errors logged to normal logging and stderr. If/when we support rebind the user can optionally configure it on listeners in the conf file, in which case failure on those listeners would trigger rebind not exit. The default (no rebind config) is still exit.
3. Listeners created via management after a successful start-up would continue to return an error status as they do now, no exit regardless of rebind config.
> Qdrouterd does not exit when service port is unavailable
> --------------------------------------------------------
>
> Key: DISPATCH-55
> URL: https://issues.apache.org/jira/browse/DISPATCH-55
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Affects Versions: 0.2
> Environment: Fedora 19, trunk build, x86_64
> Reporter: Chuck Rolke
> Fix For: 0.7.0
>
>
> When qdrouterd's port 5672 is in use then the router prints an error at startup but otherwise keeps running with no apparent open port. Log from failed startup:
> {noformat}
> Fri May 16 09:19:17 2014 CONN_MGR (INFO) Configured Listener: 0.0.0.0:amqp role=normal
> Fri May 16 09:19:17 2014 SERVER (ERROR) Driver Error 0 ((null))
> Fri May 16 09:19:17 2014 SERVER (INFO) Operational, 4 Threads Running
> {noformat}
> Startup from when the port is available have the same log without the (ERROR) line.
> Expected behavior is either
> * a qpidd-like exit-with-failure-message or
> * qdrouterd keeps trying to open the port and succeeds eventually.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org