Bela Ban

Hi Dave note that the ML is at [1]. Can you post your configuration (jgroups.xml)? Does IP:port correlate with the bind_addr you use in the transport? Can you post the startup log with TRACE enabled for TCP, GMS and the discovery protocol (e.g. TCPPING)? The fake version number might be caused by receiving garbage on one of the ports, ie. a conflict with a different process. I also suggest turn selinux and firewalling off for this test, to see if this has an impact. [1] https://groups.google.com...

Not sure I understand your topology. My comments below are therefore of a general nature. Use a Network CNI which provides IP multicast support, e.g. one mentioned in [1] Use a different discovery protocol, e.g. KUBE_PING [2] or DNS_PNG [3]. Note that you can list multiple discovery protocols in the same config (depends on the JGroups version you use). Use an external discovery service such as GossipRouter / TCPGOSSIP [4] Switch from bridged to host networking I hope these suggestions help [1] https://tanmaybatham.medium.com/multicast-in-kubernetes-challenges-solutions-and-implementation-f30c29438f2a...

First off: this config isn't correct: message_processing_policy="0" will not create a MessageProcessingPolicy (has to be "submit" or "max" (default)), so incoming messages will get dropped, with an exception If UNICAST3 is removed, messages will indeed get received in the right order, but the thread pool might reorder their delivery, so correct ordering is not guaranteed The big problem here is that you're using JGroups in a client-server mode, which is not what the idea is: peer-to-peer. Various...

On 15.09.21 12:45, Rainer Stransky wrote: I am using a small Notification application based on "JGroups V5.0.0 Final" in a small office Windows 10 network. All worked perfect. Since a view weeks ago a new security policy has now enabled the Windows 10 firewall and my notification application was not able to find the other instances. I have now changed the Windows 10 firewall settings. In the extended setting I changed the incoming rules for the used "OpenJDK Platform binary" to allow incomming connections....

You need to set this attribute directly in the GossipRouter: GossipRouter g=new GossipRouter(...); g.maxLength(100_000); On 19.05.21 19:50, Michael Cirioli wrote: One more question - my understanding is that the gossip router is used for TCP communication, so setting max_length on TCP_NIO2 (for example) should ensure that no messages larger than max_length actually get routed, right? Also, I am not sure if you should expect to be able to set max_length for <tcpgossip ...="">, it fails for me with...

On 19.05.21 17:48, Michael Cirioli wrote: Thanks for the quick turnaround! I've grabbed the latest (4.2.15) and I am now able to use the new attribute. My simple test shows that it is working as expected! Excellent! Bear in mind that the main use case was that a (possibly malicious) service connects to a JGroups port incidentally, and should not cause the service to allocate too much memory. Cheers, thanks again -mike cirioli On 5/19/2021 8:57:12 AM, Michael Cirioli mikecirioli@gmail.com mikecirioli@gmail.com...

Note that I just released 4.2.15.Final. Should take ~1hr to sync to maven central. Cheers, On 19.05.21 15:27, Michael Cirioli wrote: Bela - lol, no worries! it happens to the best of us :) Thank you! -mike cirioli On 5/19/2021 2:17:23 AM, Bela Ban belaban@users.sourceforge.net belaban@users.sourceforge.net wrote: Hi Michael I'm embarassed: max_length is only used by GossipRouter, but not by either TCP or TCP_NIO2! :-) I created [1] to change this. Cheers, [1] https://issues.redhat.com/browse/JGRP-2559...

Hi Michael I'm embarassed: max_length is only used by GossipRouter, but not by either TCP or TCP_NIO2! :-) I created [1] to change this. Cheers, [1] https://issues.redhat.com/browse/JGRP-2559 On 18.05.21 23:56, Michael Cirioli wrote: I am using org.jgroups:jgroups:jar:4.2.14.Final, my configuration file looks like this excerpt: <config xmlns="urn:org:jgroups" ="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemalocation="urn:org:jgroups &lt;a href=" http:="" www.jgroups.org="" schema=""...