This reminds me of this tip from "The Pragmatic Programmer":
"We worked on a project where a senior engineer was convinced that the
select system call was broken on Solaris. No amount of persuasion or
logic could change his mind (the fact that every other networking
application on the box worked fine was irrelevant). He spent weeks
writing workarounds, which, for some odd reason, didn't seem to fix
the problem. When finally forced to sit down and read the
documentation on select, he discovered the problem and corrected it in
a matter of minutes. We now use the phrase "select is broken" as a
gentle reminder whenever one of us starts blaming the system for a
fault that is likely to be our own."
Regards,
Pieter
On Wed, Nov 25, 2009 at 9:04 AM, Dannes Wessels <di...@ex...> wrote:
> All,
>
> Lat week I found the following logging in std out:
>
> "10028020@qtp-2102960-1 - Acceptor0
> SelectChannelConnector@0.0.0.0:8080] INFO org.mortbay.log - seeing JVM
> BUG(s) - cancelling stOps==0"
>
>
> Fortunately my friend google helped me here. Check the code in :
>
> http://dev.eclipse.org/mhonarc/lists/jetty-commit/msg00930.html
>
> here you see comments in the code like
>
> "// BLOODY SUN BUG !!! Try refreshing the entire selector."
>
> and expressions like
>
> "else if (_jvmBug%32==31) // heuristic attempt to cancel key
> 31,63,95,... loops"
>
>
> The jetty folks are happy to share their frustrations with us :-)
>
> regards
>
> Dannes
>
|
