I'm referring to that: on Windows my selector, after a wakeup(), doesn't block anymore and then hogs my cpu time.
This is for an end-course project, where it is only required to work in our linux network, so in theory I can just ignore the problem and live an happy life, but I want to fix it anyway.
Anyone could suggest me a workaround? I've implemented a "loop detector" (just counts how many times it loops without select a selectionkey) and then reconstruct the selector, but it don't work.