[jboss-jira] [JBoss JIRA] (WFLY-8655) TCPPING/TCPGOSSIP not configurable via outbound-socket-binding capability references
Paul Ferraro (JIRA)
issues at jboss.org
Thu Apr 27 09:26:01 EDT 2017
[ https://issues.jboss.org/browse/WFLY-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ferraro moved JBEAP-10586 to WFLY-8655:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8655 (was: JBEAP-10586)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
(was: Clustering)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR17)
> TCPPING/TCPGOSSIP not configurable via outbound-socket-binding capability references
> ------------------------------------------------------------------------------------
>
> Key: WFLY-8655
> URL: https://issues.jboss.org/browse/WFLY-8655
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
>
> TCPPING and TCPGOSSIP are notoriously awkward to configure and manage. This can be addressed by using capability references to outbound-socket-bindings.
> e.g.
> <sockets-protocol type="TCPPING" outbound-socket-bindings="binding1 binding2"/>
> Additionally, TCPPING port_range can be auto-configured from the port_range specified by the transport.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list