qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-6096) java broker doesn't indicate that port is already in use
Date Thu, 05 Mar 2015 12:04:38 GMT

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

Robbie Gemmell commented on QPID-6096:
--------------------------------------

Yep, which is reasonable enough, we added the 'Management Mode' for similar reason (needed
console access to enable though, so not quite as easily accessed when you need it) as well
as allowing configuration without the broker listening for AMQP traffic. It just needs to
be more obvious something is wrong. I wasnt aware of the behaviour disparity between AMQP
and management ports. Perhaps special casing port failures to halt startup but other things
not to could be a middle ground option.

> 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


Mime
View raw message