[
https://issues.apache.org/jira/browse/QPID-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13869436#comment-13869436
]
ASF subversion and git services commented on QPID-5472:
-------------------------------------------------------
Commit 1557683 from [~k-wall] in branch 'qpid/trunk'
[ https://svn.apache.org/r1557683 ]
QPID-5472: [Java Broker] Connection model object attribute PORT should return
the name of the Port
* Added REST system test for the above
* Also addressed review comments from Andrew MacBean (namely,
HttpManagement#stop should chain the underlying exception).
> 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: [email protected]
For additional commands, e-mail: [email protected]
