selector.select() in NIO and high cpu usage

[Arandil]

Hello,

I have a 'little' problem with Selector.select() method. I was using NIO in
my app successfully till the time I had to connect to about 50 hosts
simulateously... Everything works, but every thread I use to wait for data
from remote host is using very much CPU (even when no data is being transfered).
I used profiler to find out which method is faulty. I found out, that my problem
is in Selector.select() method. It is taking almost all available CPU power,
no matter if there is any data waiting...

Is there any way to reduce the CPU load to the minimum or do I have to use
other method than Selectors?

Thanks in advance and best regards,
Arandil.

 

[Arandil]

Is there any way to reduce the CPU load to the minimum or do I have to use
other method than Selectors?

Mea culpa, my fault... Profiler did say that select() was taking whole CPU load,
but that's not true... Indeed, there was a loop, but it was caused by my
overlooking of the problem - I had a loop, which was appending every bytebuffer
into one byte array (when there were more than one). It was looping, when
read() function didn't return 0. And this is the fault - n != 0, not n > 0...
Forgot about -1 (end of stream) :/

Sorry for garbage, and not cancelling to get this post to google - maybe
someone will need it one day...

Best regards, Arandil.