-
Suggestion
-
Resolution: Answered
-
None
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
It may be of interest to some of the customers to replace Multicast with "Well known Addresses" using Unicast.
It could assist in bypassing known problems caused by using multicast and smart 'Cisco' switches, for example. Also some companies policy may not allow or support multicasting in their departments.
[Cluster Troubleshooting page|
http://confluence.atlassian.com/display/DOC/Cluster+Troubleshooting] suggests that some customers are using WKA instead of Multicast. The page in question:
The Tangosol docs suggesting to place the specified changes in confluence_home/tangosol-coherence-override.xml
<unicast-listener>
<!--
Note: Specifying one or more "well known" addresses (WKA) will disable
all multicast communication. In this case, for a member to join the cluster
it will either have to be a WKA or there will have to be at least one WKA
member running.
Note: The "localhost" setting may not work on systems that define
localhost as the loopback address; in that case, specify the machine
name or the specific IP address.
-->
<well-known-addresses>
<socket-address id='1'>
<address/>
<port>8088</port>
</socket-address>
</well-known-addresses>
<address>localhost</address>
<port>8088</port>
<port-auto-adjust>true</port-auto-adjust>
<packet-buffer>
<maximum-packets>1428</maximum-packets>
</packet-buffer>
<priority>8</priority>
</unicast-listener>
- is incorporated by
-
- Closed
- is related to
-
- Closed
- relates to
-
- Closed
-
- Closed
