You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2015/03/05 12:26:39 UTC

[jira] [Commented] (QPID-6096) java broker doesn't indicate that port is already in use

    [ https://issues.apache.org/jira/browse/QPID-6096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348627#comment-14348627 ] 

Rob Godfrey commented on QPID-6096:
-----------------------------------

QPID-6194 provides a mechanism to make the broker fail to startup if ports are in use (or there is any other error in configuration that prevents a clean startup).

Personally I'd be quite happy to make failure the default option, and continuing (while reporting an error) occur only if you explicitly set the environment/system/context property broker.failStartupWithErroredChild to false



> java broker doesn't indicate that port is already in use
> --------------------------------------------------------
>
>                 Key: QPID-6096
>                 URL: https://issues.apache.org/jira/browse/QPID-6096
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.30, 0.31
>            Reporter: Gordon Sim
>            Priority: Minor
>
> If you have something listening on 5672 when you start the java broker, it will start but won't indicate that it can't listen to that port. Would be nice to have an error or something as it will I suspect be an increasingly common issue as more things may be listening on that port.



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