it does seem worth filing in JIRA - we can look at the NPE and perhaps it is a concurrency problem.
I'm not sure about the latter error you see, why would anything be trying to delete the contents of the Archiva installation? - Brett On 11/02/2008, aldana <[EMAIL PROTECTED]> wrote: > > hi, > > we are using cruise control which is doing nigthly checks (around 20 > projects). with this the builds are crashing and archiva stops to respond at > given port (connection refused). i need to restart the server and then it > works again. i guess that continuum is having problems with parallel > requests. > the first thing i can think of is to set the time gap of single projects' > builds a bit higher (currently it is 1 minute, which doesn't seem to be > enough to prevent collisions). > never the less in future it would be nice if archiva could handle such > settings. > do you think that this could be an issue for JIRA? > > following error-log bits: > *************************************************** > INFO | jvm 1 | 2008/02/08 23:00:18 | 2008-02-08 23:00:18,732 [Thread-5] > ERROR > org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:database-update - > Error executing task > INFO | jvm 1 | 2008/02/08 23:00:18 | > edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: > java.lang.NullPointerException > INFO | jvm 1 | 2008/02/08 23:00:18 | at > edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299) > INFO | jvm 1 | 2008/02/08 23:00:18 | at > edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118) > INFO | jvm 1 | 2008/02/08 23:00:18 | at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:159) > INFO | jvm 1 | 2008/02/08 23:00:18 | at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:127) > INFO | jvm 1 | 2008/02/08 23:00:18 | Caused by: > java.lang.NullPointerException > INFO | jvm 1 | 2008/02/08 23:00:18 | at > org.apache.maven.archiva.database.updater.ProcessArchivaArtifactClosure.execute(ProcessArchivaArtifactClosure.java:56) > INFO | jvm 1 | 2008/02/08 23:00:18 | at > org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388) > INFO | jvm 1 | 2008/02/08 23:00:18 | at > org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateProcessed(JdoDatabaseUpdater.java:170) > INFO | jvm 1 | 2008/02/08 23:00:18 | at > org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateAllProcessed(JdoDatabaseUpdater.java:111) > INFO | jvm 1 | 2008/02/08 23:00:18 | at > org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor.executeTask(ArchivaDatabaseUpdateTaskExecutor.java:78) > INFO | jvm 1 | 2008/02/08 23:00:18 | at > > > ************************************************** > INFO | jvm 2 | 2008/02/09 10:30:54 | Caused by: java.io.IOException: > File > C:\Programme\apache-archiva-1.0.1\bin\windows-x86-32\..\..\services\plexus-appserver-service-jetty-2.0-alpha-8\lib\servlet-api-2.4.jar > unable to be deleted. > INFO | jvm 2 | 2008/02/09 10:30:54 | at > org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1165) > INFO | jvm 2 | 2008/02/09 10:30:54 | at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > INFO | jvm 2 | 2008/02/09 10:30:54 | at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1328) > INFO | jvm 2 | 2008/02/09 10:30:54 | at > org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > > > > > > > > ----- > manuel aldana > aldana((at))gmx.de > homepage: http://www.aldana-online.de > -- > View this message in context: > http://www.nabble.com/stability-problems-tp15407339p15407339.html > Sent from the archiva-users mailing list archive at Nabble.com. > > -- Brett Porter Blog: http://blogs.exist.com/bporter/
