[
https://issues.apache.org/jira/browse/ARTEMIS-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987463#comment-14987463
]
ASF subversion and git services commented on ARTEMIS-292:
---------------------------------------------------------
Commit b73e61ac528443b7978a9c70e5b76a1a0b8aeefc in activemq-artemis's branch
refs/heads/master from [~andytaylor]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=b73e61a ]
ARTEMIS-292 - fix isSameHost on TransportConfiguration
Ive renamed the current isSameHost method to isSameparams as thats what it
checked and added a new method for isSameHost that checks the appropriate
params for the connector. Ive changed ClientSessionFactoryImp to use this to
correct the behaviour.
https://issues.apache.org/jira/browse/ARTEMIS-292
> isSameHost doesn't work
> -----------------------
>
> Key: ARTEMIS-292
> URL: https://issues.apache.org/jira/browse/ARTEMIS-292
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.1.0
> Reporter: Andy Taylor
> Assignee: Andy Taylor
>
> TransportConfiguration.isSameHost(...) does a comparison on all the params
> which is incorrect for some scenarios. It needs to check the host/port or
> serverID but only be changed for the calls that needs it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
