On Mon, Jan 6, 2020 at 1:27 PM Rathore, Rajendra <rarath...@ptc.com> wrote:

> Hi Team,
>
>
>
> We are facing performance issue during 
> *org.apache.tomcat.util.net.NioBlockingSelector.write
> API call, *,most of our thread stuck and spending more time in that API,
> you can check below screenshot for more details.
>
>
>
>
>
>
>
>
>
> We debug the code and found that NioChannel.write method return 0(Zero)
> value, in that case our threads are stuck, Please  let us know why this
> happen.
>

As NIO is non blocking IO, 0 bytes written means there's a backlog and
output will block in NioBlockingSelector since it emulates blocking IO
there. It should not actually consume CPU, just wait until there's a poller
event indicating writing data may continue.

Rémy


>
>
> Please let me know if you need more details.
>
>
>
>
>
> Thanks and Regards,
>
> Rajendra Rathore
>
> 9922701491
>
>
>

Reply via email to