Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-1199

NullPointerException in IndexModifier.close()

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0, 2.3.1
    • Fix Version/s: 2.3.2, 2.4
    • Component/s: core/index
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      We upgraded from Lucene 2.0.0. to 2.3.1 hoping this would resolve this issue.

      http://jira.codehaus.org/browse/MRM-715

      Trace is as below for Lucene 2.3.1:
      java.lang.NullPointerException
      at org.apache.lucene.index.IndexModifier.close(IndexModifier.java:576)
      at org.apache.maven.archiva.indexer.lucene.LuceneRepositoryContentIndex.closeQuietly(LuceneRepositoryContentIndex.java:416)
      at org.apache.maven.archiva.indexer.lucene.LuceneRepositoryContentIndex.modifyRecord(LuceneRepositoryContentIndex.java:152)
      at org.apache.maven.archiva.consumers.lucene.IndexContentConsumer.processFile(IndexContentConsumer.java:169)
      at org.apache.maven.archiva.repository.scanner.functors.ConsumerProcessFileClosure.execute(ConsumerProcessFileClosure.java:51)
      at org.apache.commons.collections.functors.IfClosure.execute(IfClosure.java:117)
      at org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388)
      at org.apache.maven.archiva.repository.scanner.RepositoryContentConsumers.executeConsumers(RepositoryContentConsumers.java:283)
      at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferFile(DefaultRepositoryProxyConnectors.java:597)
      at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:157)
      at org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSideRelocation(ProxiedDavServer.java:447)
      at org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFromProxies(ProxiedDavServer.java:354)
      at org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:189)
      at org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119)
      at org.apache.maven.archiva.web.repository.RepositoryServlet.service(RepositoryServlet.java:155)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

        Activity

        Hide
        mikemccand Michael McCandless added a comment -

        Were there any prior exceptions before you hit this one?

        It's hard to see how IndexModifier could have both its indexReader & indexWriter null, unless it had hit an exception on re-opening one of them.

        Show
        mikemccand Michael McCandless added a comment - Were there any prior exceptions before you hit this one? It's hard to see how IndexModifier could have both its indexReader & indexWriter null, unless it had hit an exception on re-opening one of them.
        Hide
        brettporter Brett Porter added a comment -

        in my case there weren't any from Lucene - I came to the same conclusion and couldn't understand why this would be. The only other thought is if close() gets called twice but I couldn't see that in our code either.

        Show
        brettporter Brett Porter added a comment - in my case there weren't any from Lucene - I came to the same conclusion and couldn't understand why this would be. The only other thought is if close() gets called twice but I couldn't see that in our code either.
        Hide
        mikemccand Michael McCandless added a comment -

        OK I just committed a defensive check that indexReader != null before we close it.

        But note that IndexModifier is now deprecated and will be removed in 3.0.

        Show
        mikemccand Michael McCandless added a comment - OK I just committed a defensive check that indexReader != null before we close it. But note that IndexModifier is now deprecated and will be removed in 3.0.
        Hide
        hossman Hoss Man added a comment -

        targeted for 2.3.2 bug fix release

        Show
        hossman Hoss Man added a comment - targeted for 2.3.2 bug fix release

          People

          • Assignee:
            Unassigned
            Reporter:
            jameswdumay James William Dumay
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development