Switch to NIO[2]

[michaelklishin]

Reported and discussed in some depth on rabbitmq-discuss.

Internal bug tracker: #23327.

The only solution is switching to NIO. NIO would yield little improvement for the client the way it works today but worth moving to for this issue.

[arunvisw]

did we get this feature in?

[michaelklishin]

@arunvisw we close issues that are fixed or no longer relevant for other reasons. This one is not closed ;)

[arunvisw]

Would really appreciate if you can suggest some work arounds

[michaelklishin]

The original thread mentions a workaround.

[Hronom]

I were any progress on solving blocks by timeout?

[michaelklishin]

@Hronom I don't understand what "blocks by timeout" means but there is no way to avoid Socket#write blocking in some cases without a really ugly workaround provided in a thread linked above. The right thing to do is to switch to NIO and since this issue is open, that is not done.

[Hronom]

So switching to NIO helps to solve situation when Channel#basicPublish block thread where it called without any notification about that connection slowed down by flow state?

[michaelklishin]

@Hronom please get familiar with the original mailing list report. This has no relation to internal flow control (or generally speaking, flow control period). While flow control may make this more visible, it can be reproduced without flow control.