You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by franz1981 <gi...@git.apache.org> on 2018/07/03 10:38:32 UTC
[GitHub] qpid-jms pull request #:
Github user franz1981 commented on the pull request:
https://github.com/apache/qpid-jms/commit/7750a1c27589261b197d7b746506e19d8771b145#commitcomment-29578656
In qpid-jms-client/src/main/java/org/apache/qpid/jms/provider/amqp/AmqpProvider.java:
In qpid-jms-client/src/main/java/org/apache/qpid/jms/provider/amqp/AmqpProvider.java on line 136:
Netty allows to query efficiently the backpressure of the I/O network layer using:
- Channel:isWritable (Channel::bytesBeforeUnwritable/Channel::bytesBeforeWritable too)
- managing [channelWritabilityChanged](https://netty.io/4.0/api/io/netty/channel/ChannelInboundHandler.html#channelWritabilityChanged-io.netty.channel.ChannelHandlerContext-) events, but it works if you are in EventLoop
Channel::isWritable is dependent by the Netty configuration of ChannelOption.WRITE_BUFFER_HIGH_WATER_MARK and ChannelOption.WRITE_BUFFER_LOW_WATER_MARK and are directly related to the backpressure provided by the socket writer ie it is directly related to TCP backpressure and the capacity of the other peer (eg the broker) to read enough data to let the socket buffer able to receive the data on the netty write buffer.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org