[
https://issues.apache.org/jira/browse/ARTEMIS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426341#comment-16426341
]
ASF subversion and git services commented on ARTEMIS-1779:
----------------------------------------------------------
Commit 0bd99dfff7c297953f03fa9b06f27305fc1a1341 in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=0bd99df ]
ARTEMIS-1779 Fixing CoverityScan finding
There was a logic to validate if member is null.
Which seemed a bit weird considering the else would throw a NPE.
Fixing it proactively based on Coverity-scan findings.
> ClusterConnectionBridge may connect to other nodes than its target
> ------------------------------------------------------------------
>
> Key: ARTEMIS-1779
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1779
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Priority: Major
> Fix For: 2.5.1
>
>
> The cluster connection bridge has a TopologyListener and connects to a new
> node each time it receives a nodeUp() event. It needs to put a check here to
> make sure that the cluster bridge only connects to its target node and it's
> backups.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
