Hi Gordon, yes, it looks exactly like the issue described in QPID-4524. It seems strange to me that the issue was closed with a statement - expected behavior. I have increased the sync_op_timeout to 5 minutes, but it just delayed the same error on the client. It is also not a store performance problem, since I can send 300 messages (all 1MB size) using C++ client in under a minute without any problem (using async sender). I am attaching logs again.
nosync_6.log <http://qpid.2158936.n2.nabble.com/file/n7644270/nosync_6.log> nosync_cpp.log <http://qpid.2158936.n2.nabble.com/file/n7644270/nosync_cpp.log> To me it seems like a misunderstanding between Java JMS client and C++ broker when using 0-10 protocol. It cannot be the case that broker is simply not able to process two consecutive 1MB messages within 5 minutes. I can understand that with 1MB (and more) messages the async mode doesn't bring much performance gain, however it should work. Thanks. -- View this message in context: http://qpid.2158936.n2.nabble.com/Unable-to-send-1MB-messages-in-asynchronous-mode-tp7643793p7644270.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
