Clebert Suconic wrote:
// NAM: A bit of a hack to disable large messages - virus scanner playing havoc with performance
factory.setMinLargeMessageSize(Integer.MAX_VALUE);
^^ if you send a large message, you will be immediately out of credits, what *will* be causing your issue.
If you want to do this, disable producer flow control.
Ok. How large is "large"? Will it be the default value for producer-window-size? (64 *1024)?
So, sending a message greater than 64K would block?
If so, then I guess that explains it.
Thanks a lot for the help.
Cheers.
you need to keep large > Producer-window-size anyway.
Large is relative. We consider 100K as large, but you can adjust to your business requirements.
Clebert Suconic wrote:
you need to keep large > Producer-window-size anyway.
Large is relative. We consider 100K as large, but you can adjust to your business requirements.
Hi Clebert, can you clarify that first bit?
I need to keep what greater than producer-window-size?
(or did you mean MinLargeMessageSize must be < producer-window-size?)
I understand Large is relative.
Im just wondering how big my messages would have to have been to end up in a deadlock situation... our message size doesnt change much.