lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4855) Potential exception in TermInfosWriter#initialize() swallowed makes debugging hard
Date Mon, 29 Apr 2013 10:50:18 GMT


Michael McCandless commented on LUCENE-4855:

OK, thanks for bringing closure Chris!
> Potential exception in TermInfosWriter#initialize() swallowed makes debugging hard
> ----------------------------------------------------------------------------------
>                 Key: LUCENE-4855
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/index
>    Affects Versions: 3.6.2
>         Environment: Hotspot 1.6.0_31 on Linux 64-bit
>            Reporter: Chris Gioran
>            Priority: Minor
> TermInfosWriter#initialize() can potentially fail with an exception when trying to write
any of the values in the try block. If that happens the finally clause will be called and
that may also fail during close(). This exception will mask the original one potentially hiding
the real cause and making debugging such failures difficult.
> My particular case involves failing the first write in the initialize() and close() failing
the seek. My code receives:
> Caused by: Illegal seek
>         at Method) ~[na:1.6.0_31]
>         at$
>         at org.apache.lucene.index.TermInfosWriter.close(
>         at org.apache.lucene.util.IOUtils.close(
> which provides no indication as to why the initialization failed. The above stack trace
has been created with lucene version 3.5.0 but the exception handling is still the same in

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message