[
https://issues.apache.org/jira/browse/QPID-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547345#comment-13547345
]
Andrew Stitcher commented on QPID-4315:
---------------------------------------
This issue has been fixed by changing the way that outgoing connections from a
broker get their name. They now get their name for the name of the link that
brings up the connection. This means that when connection notifications come
back to the link registry there is no ambiguity about which link is the correct
one to direct the notification to.
The default generated names of all connections now have "qpid." prepended to
avoid user specified names being able to clash (as the user is not allowed to
use names starting with "qpid.")
> SSL federation doesn't work when used with hostname rather than IP
> ------------------------------------------------------------------
>
> Key: QPID-4315
> URL: https://issues.apache.org/jira/browse/QPID-4315
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.14, 0.16, 0.18
> Reporter: Gordon Sim
> Assignee: Andrew Stitcher
> Fix For: 0.21
>
> Attachments: SslSocket.patch
>
>
> The link is established but the link registry is unable to match the link to
> the connection as the management id used for the connection uses the IP
> address and not the hostname as specified.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
