[
https://issues.apache.org/jira/browse/DISPATCH-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802193#comment-15802193
]
ASF subversion and git services commented on DISPATCH-55:
---------------------------------------------------------
Commit a88046c3bbe78d259c644f87818a3e7f727a2429 in qpid-dispatch's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=a88046c ]
DISPATCH-55 - Fail and exit if a configured listener fails to bind. This only
occurs on the initial configuration. Listeners added via management that fail
to bind shall only raise an ERROR log.
> 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
> Assignee: Ted Ross
> Fix For: 0.8.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: [email protected]
For additional commands, e-mail: [email protected]