On 07/05/2013 02:52 PM, Gordon Sim 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.
This would also affect flow controlled queues, since the flush again
would respond with a session-completed that does not include all
outstanding transfers.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
