continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoff Gibbs (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-551) NullPointerException in DefaultContinuum
Date Mon, 16 Jan 2006 10:35:01 GMT
    [ http://jira.codehaus.org/browse/CONTINUUM-551?page=comments#action_55985 ] 

Geoff Gibbs commented on CONTINUUM-551:
---------------------------------------

Having used the workaround above the schedules now run when running continuum from the command
line, but not when continuum is running as a Windows service.

The log simply contains:
{noformat}INFO   | jvm 1    | 2006/01/16 10:25:00 | 2006-01-16 10:25:00,031 [scheduler1_Worker-14]
INFO  SchedulesActivator             - >>>>>>>>>>>>>>>>>>>>>
Executing build job (4testing)...
INFO   | jvm 1    | 2006/01/16 10:25:00 | 2006-01-16 10:25:00,078 [scheduler1_Worker-14] INFO
 ContinuumStore:jdo             - nb result : 1{noformat}

> NullPointerException in DefaultContinuum
> ----------------------------------------
>
>          Key: CONTINUUM-551
>          URL: http://jira.codehaus.org/browse/CONTINUUM-551
>      Project: Continuum
>         Type: Bug

>   Components: Core system
>     Versions: 1.0.2
>     Reporter: Tim McCune

>
>
> I tried adding 2 Maven 1.x projects to Continuum from the same POM, then changing their
names.  Changing their names simply failed (see CONTINUUM-548) and Continuum changed them
back.  After this, Continuum simply stopped building either of the projects.  Here is the
exception I found in the log:
> Jan 6, 2006 12:00:00 PM org.quartz.core.JobRunShell run
> INFO   | jvm 1    | 2006/01/06 12:00:00 | SEVERE: Job DEFAULT.DEFAULT_SCHEDULE threw
an unhandled Exception:
> INFO   | jvm 1    | 2006/01/06 12:00:00 | java.lang.NullPointerException
> INFO   | jvm 1    | 2006/01/06 12:00:00 |       at org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:368)
> INFO   | jvm 1    | 2006/01/06 12:00:00 |       at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:66)
> INFO   | jvm 1    | 2006/01/06 12:00:00 |       at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
> INFO   | jvm 1    | 2006/01/06 12:00:00 |       at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
> INFO   | jvm 1    | 2006/01/06 12:00:00 | Jan 6, 2006 12:00:00 PM org.quartz.core.ErrorLogger
schedulerError
> INFO   | jvm 1    | 2006/01/06 12:00:00 | SEVERE: Job (DEFAULT.DEFAULT_SCHEDULE threw
an exception.
> INFO   | jvm 1    | 2006/01/06 12:00:00 | org.quartz.SchedulerException: Job threw an
unhandled exception. [See nested exception: java.lang.NullPointerException]
> INFO   | jvm 1    | 2006/01/06 12:00:00 |       at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> INFO   | jvm 1    | 2006/01/06 12:00:00 |       at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
> INFO   | jvm 1    | 2006/01/06 12:00:00 | * Nested Exception (Underlying Cause) ---------------
> INFO   | jvm 1    | 2006/01/06 12:00:00 | java.lang.NullPointerException
> INFO   | jvm 1    | 2006/01/06 12:00:00 |       at org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:368)
> INFO   | jvm 1    | 2006/01/06 12:00:00 |       at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:66)
> INFO   | jvm 1    | 2006/01/06 12:00:00 |       at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
> INFO   | jvm 1    | 2006/01/06 12:00:00 |       at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)

-- 
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


Mime
View raw message