You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2015/09/29 20:40:04 UTC
[jira] [Assigned] (QPID-6731) HttpManagement operational logging
does not log actual port bound when the system-allocated port is used
(port=0)
[ https://issues.apache.org/jira/browse/QPID-6731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall reassigned QPID-6731:
--------------------------------
Assignee: Keith Wall
> HttpManagement operational logging does not log actual port bound when the system-allocated port is used (port=0)
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-6731
> URL: https://issues.apache.org/jira/browse/QPID-6731
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0
> Reporter: Keith Wall
> Assignee: Keith Wall
> Priority: Minor
> Fix For: qpid-java-6.0
>
>
> When the user specifies port 0, this signals that the system is to allocate the port number. The operational log messages are intended to report the actual port bound.
> QPID-6688 introduced a regression so that the MNG-1002 logged the request port number (0), rather than the port number that was actually bound.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org