Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.1.0.DR19
Affects Version/s: 7.1.0.DR17
Component/s: Clustering
Labels:
None

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.1.0.GA
Git Pull Request:
https://github.com/jbossas/jboss-eap7/pull/1787

SFDC Cases Counter:
SFDC Cases Links:

Because we configure our JGroups transport via a socket-binding, we already leverage the port-offset feature to mitigate port conflicts - thus removing the need to rely on the port_range property. The use of port_range is troublesome from a management perspective, as it means that the actual port can differ from the ports reported by the management layer.

is cloned by

WFLY-8657 JGroups transport port_range should default to 0

Closed

relates to

JBEAP-11195 DR19 Cluster behaves differently when trying to use already used IP/port for "jgroups-udp" socket-binding

Closed

Assignee:: Paul Ferraro

Reporter:: Paul Ferraro

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2017/04/27 9:26 AM

Updated:: 2017/05/30 1:54 AM

Resolved:: 2017/05/24 7:47 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates