]
Bela Ban commented on JGRP-1931:
--------------------------------
It would make things way more complicated - as each Tabel requires an initial seqno when
being created. I don't want to fuzz around with Table, as it is a core classe required
by NAKACK2 and UNICAST3.
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).