[jboss-jira] [JBoss JIRA] (JGRP-1931) Don't drop UNICAST3 message when the window is not created

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079676#comment-13079676 ] 

Bela Ban edited comment on JGRP-1931 at 6/16/15 8:35 AM:
---------------------------------------------------------

What's the use case here ? The {{DONT_BUNDLE}} flag should be used sparingly and is actually ignored unless coupled with {{OOB}}. Note that only a few internal JGroups messages use {{DONT_BUNDLE, OOB}}.
OK, this can still hapen if you send a _regular_ and an _OOB_ message as first messages to a new member, or a member which closed its connection to us.
Retransmission of the dropped message should be quick; by default the retransmission interval in {{UNICAST3}} ({{xmit_interval}}) is 500 ms.


was (Author: belaban):
What's the use case here ? The {{DONT_BUNDLE}} flag should be used sparingly and is actually ignored unless coupled with {{OOB}}. Note that only a few internal JGroups messages use {{DONT_BUNDLE, OOB}}.

> 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/UNICAST3.java#L943). 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)