[
https://issues.apache.org/jira/browse/LUCENE-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved LUCENE-2511.
------------------------------------
Resolution: Won't Fix
2013 Old JIRA cleanup
> OutOfMemoryError should not be wrapped in an IllegalStateException, as it is
> misleading for fault-tolerant programs
> -------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-2511
> URL: https://issues.apache.org/jira/browse/LUCENE-2511
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/index
> Affects Versions: 2.4.1
> Reporter: David Sitsky
> Priority: Minor
>
> I have a program, which does explicit commits. On one occasion, I saw the
> following exception thrown:
> java.lang.IllegalStateException: this writer hit an OutOfMemoryError; cannot
> commit
> at org.apache.lucene.index.IndexWriter.prepareCommit(IndexWriter.java:4061)
> at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:4136)
> at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:4114)
> In our program, we treat all errors as fatal and terminate the program (and
> restart). Runtime exceptions are sometimes handled differently, since they
> are usually indicative of a programming bug that might be recoverable. in
> some situations.
> I think the OutOfMemoryError should not be wrapped as a runtime exception..
> as this can mask a serious issue from a fault-tolerant application.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
