[
http://jira.codehaus.org/browse/MINDEXER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262664#action_262664
]
Tamás Cservenák commented on MINDEXER-26:
-----------------------------------------
Just to clean up my previous hazy comment that contained a revelation. So yes,
it seems that {{warmUp()}}, when throws IOEx actually closes the context, but
then later a "prepare clean index" is tried, and NPEs. And all this might
happen from constructor too.
> NPE from IndexWriter.isLocked in DefaultIndexingContext.prepareCleanIndex
> -------------------------------------------------------------------------
>
> Key: MINDEXER-26
> URL: http://jira.codehaus.org/browse/MINDEXER-26
> Project: Maven Indexer
> Issue Type: Bug
> Affects Versions: 4.0.0
> Environment: VM: Java HotSpot(TM) 64-Bit Server VM, 19.0-b09,
> Java(TM) SE Runtime
> Environment, 1.6.0_23-b05
> OS: Windows 7
> Reporter: Jesse Glick
>
> http://netbeans.org/bugzilla/show_bug.cgi?id=197346 reported by a NetBeans
> user in a build embedding Maven Indexer 4.0.0.
> {noformat}
> if ( IndexWriter.isLocked( indexDirectory ) )
> {
> IndexWriter.unlock( indexDirectory );
> }
> {noformat}
> Looks like {[indexDirectory}} is null, perhaps due to {{close}} having been
> called, and this code does not check for that (other code in the same class
> does). Can probably be guarded with a simple null check?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
