[
https://issues.apache.org/jira/browse/PROTON-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237330#comment-15237330
]
ASF subversion and git services commented on PROTON-1133:
---------------------------------------------------------
Commit 619c5c7ff6f155468f472b66a60021db72af8ecf in qpid-proton's branch
refs/heads/master from [~kgiusti]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=619c5c7 ]
PROTON-1133: Reactor should not use the connection hostname as a
transport address.
This patch introduces a new reactor API for setting the host address
for a connection created via the reactor. This API is intended to
replace the existing semantics where the connection's host address is
derived via the connection's hostname setting.
> Proton C includes port number in AMQP Open hostname
> ---------------------------------------------------
>
> Key: PROTON-1133
> URL: https://issues.apache.org/jira/browse/PROTON-1133
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c, python-binding
> Affects Versions: 0.12.0
> Reporter: Chuck Rolke
> Assignee: Ken Giusti
> Fix For: 0.13.0
>
>
> A command like:
> {noformat}
> qdmanage -b amqp://u1:password@photoserver:21000 --type policyStats query
> {noformat}
> sends the port number in the hostname field of the AMQP Open:
> {noformat}
> Mon Feb 8 11:37:46 2016 SERVER (trace) [2]:0 <- @open(16)
> [container-id="34e49947-b4df-4a01-9570-0a74e9e57b5b",
> hostname="photoserver:21000", channel-max=32767]
> (/home/chug/git/qpid-dispatch/src/server.c:75)
> {noformat}
> Built in C example code using Proton only does the same thing.
> This bug originally reported at
> https://issues.apache.org/jira/browse/DISPATCH-214
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
