[
https://issues.apache.org/jira/browse/ARTEMIS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710391#comment-14710391
]
ASF GitHub Bot commented on ARTEMIS-208:
----------------------------------------
Github user gaohoward commented on the pull request:
https://github.com/apache/activemq-artemis/pull/132#issuecomment-134435057
yeah there is going to be a problem if acceptor is using 0.0.0.0. In that
case we probably need a way to find the port which the client is connected to.
We cache the brokerInfo but not the brokerURL, you can see we do send a
brokerInfo based on connection request, see method
ConnectionEntry createConnectionEntry(Acceptor acceptorUsed, Connection
connection)
I think what's need to to is to pass a copy of brokerInfo to the new
connection.
Thanks
Howard
> Fix BrokerInfo Issue
> --------------------
>
> Key: ARTEMIS-208
> URL: https://issues.apache.org/jira/browse/ARTEMIS-208
> Project: ActiveMQ Artemis
> Issue Type: Sub-task
> Components: OpenWire
> Affects Versions: 1.0.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Fix For: 1.1.0
>
>
> When a client opens a connection to broker, the broker should send back a
> BrokerInfo command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
