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 ? Rajith On Fri, Jul 5, 2013 at 9:52 AM, Gordon Sim <[email protected]> wrote: > On 07/05/2013 02:08 PM, Rajith Attapattu wrote: > >> The timeout happens when the brokers fails to respond to sync operation >> during the specified time. >> > > Does the JMS client actually sync now? In the past it only used to flush > instead, which for durable messages (which complete asynchronously) meant > it got a response that did not include all messages sent which confused it. > > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > [email protected].**org<[email protected]> > For additional commands, e-mail: [email protected] > >
