Tuesday, May 30, 2006

Finally got a reply

Today after exactly 1 year since I reported the LinkedBlockingQueue bug I got a reply for all 3. It seems that the LinkedBlockingQueue issue has been fixed in jdk 1.5_07, while the charset ones in Mustang.

1 Comments:

Blogger Martin Buchholz said...

I'm the sun engineer who addressed
both of these problems.
Here is some info from the bug
database:

6189072: Add sometimes fails after clear or drainTo in LinkedBlockingQueue 5.0u2
6307455: LinkedBlockingQueue.toArray(x) does not set "one-past" element of x to null 5.0u6
6215625: LinkedBlockingQueue.extract throws NPE 5.0u6
6189072: Add sometimes fails after clear or drainTo in LinkedBlockingQueue mustang
6215625: LinkedBlockingQueue.extract throws NPE mustang
6307455: LinkedBlockingQueue.toArray(x) does not set "one-past" element of x to null mustang
6316155: LinkedBlockingQueue: q.offer(xyz) returns false positives and/or q.remove(xyz) gives up too easily mustang


6221056: (cs) CharsetEncoder.encode(ByteBuffer) should call flush(ByteBuffer)
6227608: (cs) Charset-X-Coder.flush cannot be reinvoked in case of overflow
6228679: (cs spec) Charset-X-Coder doc suggests overriding final methods flush, reset
6231155: (cs spec) Inaccuracies in Charset-X-Coder.$code$(...) doc

6:52 AM  

Post a Comment

<< Home