[jboss-jira] [JBoss JIRA] (JGRP-1931) Don't drop UNICAST3 message when the window is not created
[
https://issues.jboss.org/browse/JGRP-1931?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1931:
--------------------------------
This is needed to know the lowest seqno of the sender. E.g. if we have sender A and
receiver B, and A sends messages 25(first) and 26, and 26 is received first, then we
don't know which seqno to use to to create the Table for A. It isn't 26, but we
don't know that it's 25 just yet, until we've received 25.
We also cannot create each table with seqno 1, as the B might have closed its connection
to A and therefore removed the table for A.
Don't drop UNICAST3 message when the window is not created
-----------------------------------------------------------
Key: JGRP-1931
URL: https://issues.jboss.org/browse/JGRP-1931
Project: JGroups
Issue Type: Bug
Affects Versions: 3.6.3
Reporter: Radim Vansa
Assignee: Bela Ban
Fix For: 3.6.4
When an application sends first two (or more) messages in parallel and the the second one
is marked as DONT_BUNDLE, usually this one arrives as the first one and is dropped (see
https://github.com/belaban/JGroups/blob/master/src/org/jgroups/protocols/...).
After first message arrives, the connection is properly set up, but we need to wait until
retransmission for the message (and other non-OOB) messages to be delivered.
In practice this behaviour should be acceptable, but it causes failures in some
time-sensitive tests (particularly in Hibernate ORM 2nd level cache).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)