From: Amy Kang <Amy.Kang_at_Sun.COM>
Date: Sat, 13 Jun 2009 09:25:52 -0700

It turned out this is not a Windows specific problem. I eventually
found a Solaris
machine with the right CPU# and speed reproduced the same problem under
stress test. It is a bug in our code - a misinterpretation of
ByteBufferFactory.allocateView()
position in ProtocolParser.

Cheers,
amy