You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrew MacBean (JIRA)" <ji...@apache.org> on 2014/01/13 12:50:52 UTC
[jira] [Resolved] (QPID-5472) Exception messages used to report
bind port failures should include port id/name/number too
[ https://issues.apache.org/jira/browse/QPID-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew MacBean resolved QPID-5472.
----------------------------------
Resolution: Fixed
Looks good to me.
> Exception messages used to report bind port failures should include port id/name/number too
> -------------------------------------------------------------------------------------------
>
> Key: QPID-5472
> URL: https://issues.apache.org/jira/browse/QPID-5472
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Andrew MacBean
> Priority: Minor
> Fix For: 0.27
>
>
> By default, the Java Broker binds to many ports on startup - separate ports for AMQP, HTTP and JMX. Unfortunately, if one of these ports is already in use, the error message reporting this fact does not, in the case of AMQP/HTTP, indicate the exact port causing the issue.
> {noformat}
> Exception during startup: org.apache.qpid.transport.TransportException: Unable to start server socket
> org.apache.qpid.transport.TransportException: Unable to start server socket
> at org.apache.qpid.transport.network.io.IoNetworkTransport.accept(IoNetworkTransport.java:149)
> {noformat}
> This change will change the error message so that the offending port number is included in message, allow the user to more easily diagnose the issue.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org