You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ted Ross (JIRA)" <ji...@apache.org> on 2014/10/14 21:40:35 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=14171404#comment-14171404 ] 

Ted Ross commented on DISPATCH-55:
----------------------------------

I believe that the correct behavior is to continue attempting to bind to the port just like an outgoing connection continually retries.

> 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
>
> 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