e() method was not called and this is the single place
where commandBytes could be decreased (to 0); otherwise isFull() will always
return true
Thanks.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Unable-to-send-1MB-messages-in-asynchronous-mode-tp7643793p7644331.html
Sen
On 19/05/16 13:47, Michal Zerola wrote:
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 clie
e 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 arch
On 18/05/16 15:00, Michal Zerola wrote:
Hi Gordon,
I have tested qpid client 0.32 and also 6.0.2 (neither is working against
C++ server).
Those are both 0-10.
If I use the same code (send three 1MB messages) against Java
Qpid broker, everything works. I am attaching logs, where you can see t
.
nosync_6.log <http://qpid.2158936.n2.nabble.com/file/n7644185/nosync_6.log>
nosync_javabroker_6.log
<http://qpid.2158936.n2.nabble.com/file/n7644185/nosync_javabroker_6.log>
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Unable-to-send-1MB-messages-in-async
On 13/05/16 13:32, Michal Zerola wrote:
I am unable to send 1MB messages using Java JMS API to Qpid (C++ broker)
v0.34 if I use asynchronous send mode (no 'sync_publish' connection option).
First message is sent normally, but the client hangs up on second
producer.send(message) call.
Was there
id.2158936.n2.nabble.com/file/n7643793/sync.log>
Messages are sent as persistent to a durable queue using topic exchange.
Thanks for help.
Michal
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Unable-to-send-1MB-messages-in-asynchronous-mode-tp7643793.html
Sent from th
