[ https://issues.jboss.org/browse/JGRP-2172?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2172: -------------------------------- A minor change in semantics wrt non-blocking flow control versus blocking flow control: if sender P sends messages 1 (700K) and 2 (300K), then blocking flow control guarantees that P1 is sent first down the stack into UNICAST3 land where it gets a seqno, then P2. Thus, P1 will be delivered before P2. However, these semantics are not guaranteed with non-blocking flow control: if we for example have 500K left, then P1 (700K) will be queued and the call returns so that P can send message 2. P2 (300K) will be sent successfully, but P1 will only get sent once we get new credits from the destination member. This means P2 may get delivered before P1. Typically this is not a problem as P1 and P2 are probably unrelated, or else P would wait for a response to P1 before sending P2 (e.g. a GET request, then a GET response and - based on the response - a PUT request). Just wanted to point this out. -- This message was sent by Atlassian JIRA (v7.2.3#72005)