[ https://issues.jboss.org/browse/JGRP-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494331#comment-13494331 ]
Bela Ban commented on JGRP-2236:
--------------------------------
Added unit test reproducing the issue to {{TableTest}}:
{code:java}
public void testGetMissingWithMaxBundleSize() {
final int max_bundle_size=64000;
final int max_xmit_req_size=(max_bundle_size -50) * Global.LONG_SIZE;
Table<Integer> table=new Table<>(10, 1000, 0);
table.add(0, 0);
table.add(1_000_000, 1_000_000);
System.out.println("table = " + table);
SeqnoList missing=table.getMissing(max_xmit_req_size);
System.out.println("missing = " + missing);
int serialized_size=missing.serializedSize();
assert serialized_size <= max_bundle_size :
String.format("serialized size of %d needs to be less than max_bundle_size of %d bytes", serialized_size, max_bundle_size);
}
{code}
> UNICAST max_xmit_req_size doesn't work
> --------------------------------------
>
> Key: JGRP-2236
> URL: https://issues.jboss.org/browse/JGRP-2236
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.1
> Reporter: Dennis Reed
> Assignee: Bela Ban
> Fix For: 4.0.9
>
>
> UNICAST3 sets max_xmit_req_size to avoid requesting too many messages to fit into the maximum message size.
> But the check is implemented incorrectly, so it is not effective.
> JGRP000029: node1: failed sending message to node2 (120314 bytes): java.io.IOException: Message too long, headers: UNICAST3: XMIT_REQ, seqno=0, TP: [cluster_name=cluster]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)