[
https://issues.apache.org/jira/browse/QPID-6096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348664#comment-14348664
]
Rob Godfrey commented on QPID-6096:
-----------------------------------
It should certainly be logged more obviously. There should also be consistency
in behaviour between AMQP ports and HTTP/JMX ports (if there is a clash on the
latter then the broker fails to start).
I think the original idea was that the broker should not stop just because some
resources that may only be used by some virtual hosts are not currently
available. Also it is possible to create erroneous configuration in the
management UI, which will (rightly) not cause the broker to exit), but then
would potentially cause the broker to fail to start on restart.
> 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: [email protected]
For additional commands, e-mail: [email protected]
