[jboss-jira] [JBoss JIRA] (WFLY-10589) Cluster is not created when allow-direct-connections-only=true
Jiri Ondrusek (JIRA)
issues at jboss.org
Mon Jun 18 09:47:00 EDT 2018
[ https://issues.jboss.org/browse/WFLY-10589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jiri Ondrusek moved JBEAP-14896 to WFLY-10589:
----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-10589 (was: JBEAP-14896)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: (was: ActiveMQ)
Affects Version/s: 14.0.0.CR1
(was: 7.0.1.CR2)
(was: 7.1.0.DR18)
(was: 7.1.0.DR19)
(was: 7.1.0.CR2)
> Cluster is not created when allow-direct-connections-only=true
> --------------------------------------------------------------
>
> Key: WFLY-10589
> URL: https://issues.jboss.org/browse/WFLY-10589
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 14.0.0.CR1
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
>
> When {{allow-direct-connections-only=true}} is configured, the cluster is not created. The problem lies in \[1\]. Comparison of {{TransportConfigurations}} should be more clever.
> \[1\]
> {code:title=ClusterConnectionImpl#nodeUP}
> // if the node is more than 1 hop away, we do not create a bridge for direct cluster connection
> if (allowDirectConnectionsOnly && !allowableConnections.contains(topologyMember.getLive().newTransportConfig(TRANSPORT_CONFIG_NAME))) {
> return;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list