[infinispan-dev] JGroups 2.7 and 2.8 work with Infinispan now

[Vladimir Blagojevic]

On 6/2/09 3:13 PM, Bela Ban wrote:
> Oh, I see ! Question: why are we dropping that message rather than 
> just blocking ? Concerns that the incoming thread pools get exhausted ?
>
> Ah, the message gets delivered by NAKACK, so we don't retransmit, but 
> if FLUSH discards it, we're screwed and never deliver that message to 
> the app.
>
> Your last statement confuses me a bit: I don't think a VIEW would get 
> sent up the stack *before* an unblock because they're tagged by seqnos 
> aren't they ? So, in other words, do we really need to discard 
> incoming mesages ?
>
No sure, we can block I guess, and wait for a latch to open, huh? No, no 
view and unblocked are ordered by sender, no problem there. It is a 
message from a third member that is the problem. It can squeeze in 
between view and unblock on member C.

WDYT?