[
https://issues.jboss.org/browse/JGRP-2236?page=com.atlassian.jira.plugin....
]
Dennis Reed commented on JGRP-2236:
-----------------------------------
UNICAST3.init sets max_xmit_req_size based on the maximum number of messages that will fit
in a SeqnoList that will serialize to the maximum bundle size.
*BUT* org.jgroups.util.Table.Missing uses it as the number of bits turned on in the
SeqnoList instead of the actual size of the SeqnoList itself (which grows without bound
based solely on the size of the Table).
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
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)