Sun Java Bugs that affect lucene

Sometimes Lucene runs amok of bugs in Sun's Java implementation. In certain cases we whittle it down to a small test case, open an issue with Sun, and hopefully Sun fixes it. In other cases we know the bug is in the JRE but we haven't narrowed it enough to open a bug with Sun. Sometimes we can work out a simple workaround in Lucene.

We try to open a Lucene mirror bug to provide details on how Lucene is affected, iterate on a compact test case for Sun, etc.

If you are affected by one of these issues that Sun has yet to accept or resolve, or simply have some spare votes, please consider adding your vote to the bug (on Sun's bug page):

Sun bug
Lucene mirror bug
Impact to Lucene
State, Priority
Workaround

6265734
LUCENE-573
NIOFSDirectory has very poor performance on Windows
Accepted, Low
Use FSDirectory or MMapDirectory on Windows

6478546
LUCENE-1566
You hit a false OutOfMemoryException when loading norms in an index with many docs
Accepted, Low
Locally patch Lucene to load large contiguous byte sequences in chunks

6707044
LUCENE-1282
Index corruption
Fixed as of 1.6.0_10, High
Lucene code base has a workaround in it

4724038
LUCENE-1658 LUCENE-1669
MMapDirectory won't close files until GC (higher transient disk usage than other FSDir); MMapDirectory returns 0 bytes when used for read/write access in remote (SMB/CIFS) mount
Cause Known, Low
Use a different Directory implementation

(No sun bug yet)
LUCENE-1342
SEGV during indexing, with Java 1.6 64 bit
(No compact test case yet)
None known

(No sun bug yet)
Discussed here and here
On 64 bit JREs, reading from files may hang (??)
(Still characterizing)
None known

6588260
LUCENE-2449
No impact as of 3.1/4.0 -- we now avoid calling new String(int[], int, int)
Fix Delivered, Bug

你可能感兴趣的:(java,windows,Lucene,sun,performance)