Michael Cirioli

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 </tcpgossip> java.lang.IllegalArgumentException: JGRP000001: configuration error: the following properties in TCPGOSSIP are not recognized: {max_length=64K} thanks...

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! thanks again -mike cirioli On 5/19/2021 8:57:12 AM, Michael Cirioli mikecirioli@gmail.com 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 wrote: Hi Michael I'm embarassed: max_length is only used by GossipRouter, but not by either TCP...

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 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 [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...

Running ant make-schema and examining the .xsd it produced and it also doesn't list a max_length attribute. On 5/18/2021 4:54:18 PM, Michael Cirioli mikecirioli@gmail.com 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="" jgroups.xsd"="">http://www.jgroups.org/schema/JGroups.xsd"></config>...

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="" jgroups.xsd"="">http://www.jgroups.org/schema/JGroups.xsd"></config> <TCP_NIO2 recv_buf_size="${tcp.recv_buf_size:128K}" send_buf_size="${tcp.send_buf_size:128K}" max_bundle_size="64K" sock_conn_timeout="300" max_length="100K" thread_pool.enabled="true"...

Which configuration sections accept that parameter? I assume tcp and nio, but my app doesn't start due to an error saying invalid attributes. Thanks -mike On Sun, May 16, 2021, 2:17 PM Bela Ban belaban@users.sourceforge.net wrote: The attribute is max_length Bela Ban -------- Original message -------- From: Michael Cirioli mikecirioli@users.sourceforge.net Date: Fri, May 14, 2021, 11:11 PM To: "[javagroups:discussion] " 18795@discussion.javagroups.p.re.sourceforge.net Subject: [javagroups:discussion]...

From what I can tell, its not listed in any .xsd and therefore my test app won't even start.

I am trying to understand how i adjust my configuration to take advantage of the fix for JGRP-2523 but am unable to figure out what element the new attribute should be applied to in my configuration. Here is my sample config: <!-- HA setup; may be overridden with $JENKINS_HOME/jgroups.xml --> <config xmlns="urn:org:jgroups" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups-4.0.xsd"> <TCP_NIO2 recv_buf_size="${tcp.recv_buf_size:128K}"...