I have been running on an updated Jaunty, and yet still got the bug. Since there have been anecdotal reports on the net of having seen it recently, I assumed it might still be around.
However... you brought me to double check, and it looks like the particular distribution of mine that has been showing the bug also has Jaunty's OpenJDK installed. OpenJDK reports "1.6.0_0", but I can't believe it's trailing Sun's by more than 2 years. Or maybe I'm wrong. Isn't the OpenJDK using the same codebase as Sun's? Rob, have you done any testing with OpenJDK at all? Anyway, I am switching that distro to Sun's JDK now, and will give it a few days running in NIO. Will keep you folk updated. -Tal On 08/12/2009 07:44 AM, Rob Heittman wrote: > This was apparently fixed in 6U4: > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=2147719 / > http://java.sun.com/javase/6/webnotes/6u4.html. > > We use Ubuntu distributions from Hardy thru Jaunty, which are tracking > much more recent JDKs; 6U11 on Hardy I believe and 6U13 on Jaunty. > Even my customers on RHEL 5.3 have 6U11 now, though. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2382899
