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 11:52:39 GMT

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

> 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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message