mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "yueyu lin" <popeye...@gmail.com>
Subject Re: About the Selector.select(int timeOut) issue
Date Thu, 19 Jul 2007 12:34:03 GMT
Yes, I know about the internal codes. But it does happen.
The most strange thing is that it was in "i/o wait" status. This may be
caused by the "poll" system call, I guess so.
I didn't try the JDK1.6 that is using "epoll" system call.

On 7/19/07, 向秦贤 <fyaoxy@gmail.com> wrote:
>
> Hi,
> Selector.select() = Selector.internalSelect(-1)
> Selector.select(int>-1) = Selector.internalSelect(int>-1)
> If just from code view, no big difference.
> os related?
> And you sure that cause by select()?
>
> Regards,
>
> 2007/7/19, yueyu lin <popeyelin@gmail.com>:
> >
> > Have you ever meet this thing?
> > When the application server use Selector.select(int timeOut) instead of
> > Selector.select() and when the server has low burden, suddenly it will
> > cause
> > the CPU to 100% usage. The highest part is I/O wait while there is no
> > connection connected with the server.
> > I noticed that will happen randomly. Sometimes it will recover and
> > sometimes
> > it will recover until there is new connection incoming.
> > When I'm using Selector.select(), it never happens again.
> > How about your experience?
> >
> > --
> > --
> > Yueyu Lin
> >
>
>
>
> --
> 向秦贤
>



-- 
--
Yueyu Lin
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message