Hi,

Please see comments in http://jira.codehaus.org/browse/MRM-1161 :)

Thanks,
Deng

On Fri, Apr 3, 2009 at 9:24 PM, kenneth.westeli...@pandora.be <
kenneth.westeli...@telenet.be> wrote:

> Dear list,
>
> I have upgraded an 1.1 Archiva install to 1.2. I have followed the upgrade
> instructions and deleted the old index to let the new version re-index the
> repositories. This went fine. After a week of operation, deploying an
> artifact sometimes fails with a 500 error. When browsing through the logs I
> can find this:
>
> 97180 [btpool0-4] ERROR org.mortbay.log - /archiva/repository/snapshots/<my
> artifact jar + path>.jar
> java.lang.NullPointerException
>        at
> org.sonatype.nexus.index.creator.DefaultIndexerEngine.endIndexing(DefaultIndexerEngine.java:63)
>        at
> org.apache.archiva.consumers.lucene.NexusIndexerConsumer.completeScan(NexusIndexerConsumer.java:210)
>        at
> org.apache.archiva.repository.scanner.functors.TriggerScanCompletedClosure.execute(TriggerScanCompletedClosure.java:48)
>        at
> org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388)
>        at
> org.apache.maven.archiva.repository.scanner.RepositoryContentConsumers.executeConsumers(RepositoryContentConsumers.java:265)
>        at
> org.apache.maven.archiva.webdav.ArchivaDavResource.executeConsumers(ArchivaDavResource.java:681)
>        at
> org.apache.maven.archiva.webdav.ArchivaDavResource.addMember(ArchivaDavResource.java:324)
>        at
> org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.doPut(AbstractWebdavServlet.java:516)
>        at
> org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.execute(AbstractWebdavServlet.java:244)
>        at
> org.apache.maven.archiva.webdav.RepositoryServlet.service(RepositoryServlet.java:124)
>        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>        at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
>        at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
>        at
> org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:413)
>        at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
>        at
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39)
>        at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
>        at
> org.apache.struts2.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:99)
>        at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
>        at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
>        at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
>        at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>        at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:722)
>        at
> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:404)
>        at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
>        at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
>        at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
>        at org.mortbay.jetty.Server.handle(Server.java:324)
>        at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
>        at
> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
>        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)
>        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
>        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
>        at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
>        at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
>
> This looks a bit like bug MRM-1076, but it's not quite the same.
> Can someone provide any insight on this issue.
>
> Many thanks in advance.
>
>
>

Reply via email to