[
https://issues.apache.org/jira/browse/QPID-6096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348659#comment-14348659
]
Robbie Gemmell commented on QPID-6096:
--------------------------------------
Although, even just making the errored state more visible would be a
significant improevement, perhaps by adding colour in the web ui and logging
the failure to bind on the startup console output rather than it only being
discoverable there by omission of the 'listening on port' line.
> 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]
