On 07/05/2013 02:59 PM, Rajith Attapattu wrote:
The JMS client will issue a "Flush" when ever it reached the byte or
command limit.
I incorrectly stated it as a "Sync".
I believe the peer is not obligated to respond immediately to a flush the
way it should for a sync ?
It is not obligated to wait for all outstanding commands to complete
before responding, indeed the intention is that it not wait, but simply
send what is complete at the point of flushing.
If I recall correctly in the past at least the JMS client did not then
reflush (or sync) later, but simply timed out based on the initial
response to the flush. Is that still the case or was it fixed?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
