[
https://issues.jboss.org/browse/WFCORE-4459?page=com.atlassian.jira.plugi...
]
Radoslav Husar moved EAP7-1250 to WFCORE-4459:
----------------------------------------------
Project: WildFly Core (was: EAP 7 Planning Pilot)
Key: WFCORE-4459 (was: EAP7-1250)
Issue Type: Feature Request (was: Requirement)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow
2.0)
Component/s: (was: Clustering)
EAP PT Pre-Checked (PC): (was: TODO)
Target Release: (was: 7.backlog.GA)
EAP PT Community Docs (CD): (was: TODO)
EAP PT Product Docs (PD): (was: New)
EAP PT Test Dev (TD): (was: TODO)
EAP PT Docs Analysis (DA): (was: TODO)
EAP PT Test Plan (TP): (was: TODO)
EAP PT Analysis Document (AD): (was: TODO)
outbound-socket-binding element should allow grouping to be
referenced by JGroups socket-discovery-protocol
-----------------------------------------------------------------------------------------------------------
Key: WFCORE-4459
URL:
https://issues.jboss.org/browse/WFCORE-4459
Project: WildFly Core
Issue Type: Feature Request
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Priority: Major
JGroups configuration can use two different ways to configure cluster detection
------ older configuration is via protocol properties --
<protocol type="TCPPING">
<property name="initial_hosts">host[7600]</property>
------ new configuration via socket reference
<socket-discovery-protocol type="TCPPING" socket-bindings="ref-a
ref-b"/>
...
<outbound-socket-binding name="ref-a">
<remote-destination host="127.0.0.1" port="7600"/>
</outbound-socket-binding>
-----------
with the old option it is possible to use an expression to set all hosts in a cluster.
The new one need to have all outbound connections listed which is harder to maintain.
As an administrator I want to have the possibility to group the connections and only have
one reference and the number of connections can be vary without changing multiple point in
the configuration.
So a configuration like this would enhance that
<outbound-socket-binding-group>
<outbound-socket-binding name="ref-a">
<remote-destination host="host1" port="7600"/>
</outbound-socket-binding>
<outbound-socket-binding name="ref-b">
<remote-destination host="host2" port="7600"/>
</outbound-socket-binding>
</outbound-socket-binding-group>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)