Dealing with slow client

["Trustin Lee (이희승)"]

Hi Srinivas,

You can check if the write queue is filled up via Channel.isWritable().
 There are high/low watermark values in NioSocketChannelConfig, which
allows you to configure when Channel.isWritable() starts to return false
(or true).

Please let me know if the documentation is not sufficient in the Javadoc.

HTH,
Trustin

Palthepu, Srinivas wrote:
> Hi
> 
> I am trying to understand the implication on the server of having a few
> of the clients that are slow compared to the rest when using Netty.
> 
> Server keeps submitting write requests to the channel and if the client
> is not retrieving fast enough at some point I assume the writes gets
> 
> Queued up inside the Netty.  This will cause the memory tied up. I want
> to detect such clients and disconnect them if they are too slow.
> 
> Is there a way I can query Netty to give me outstanding write requests
> on a channel? Or should I keep monitoring the channel write completes
> 
> and compute the time to complete the writes.
> 
>  
> 
> Thanks for the help
> 
> Srini
> 
> ------------
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users

-- 
what we call human nature in actuality is human habit
http://gleamynode.net/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/netty-users/attachments/20100428/fce2c14f/attachment-0001.bin