Continuum

scheduler not calling scm's update command at scheduled time

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.2
  • Fix Version/s: 1.0.3
  • Component/s: Core system
  • Labels:
    None
  • Environment:
    xp, starteam
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

The log shows the timer fires correctly but no attempt to call scm's update command to detect changes

4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - < Continuum 1.0.2 started! >
4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - ----------------------------
4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - \ __
4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - \ (oo)_______
4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - (__)\ )\/\
4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - ||----w |
4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - || ||
4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum -
4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum -
4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.initialization.ContinuumInitializer - Continuum initializer running ...
4985 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.build.settings.SchedulesActivator - Activating schedules ...
5016 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.build.settings.SchedulesActivator - Mon Dec 19 05:00:00 PST 2005
5016 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.build.settings.SchedulesActivator - Tue Dec 20 00:01:00 PST 2005
5016 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.build.settings.SchedulesActivator - Thu Jan 01 10:15:00 PST 2099
5016 [WrapperSimpleAppMain] INFO org.codehaus.plexus.PlexusContainer - Loading on start [role,roleHint]: [org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor,build-project]
5344 [WrapperSimpleAppMain] ERROR org.codehaus.plexus.velocity.VelocityComponent - ResourceManager.getResource() parse exception: org.apache.velocity.exception.ParseErrorException: Lexical error: org.apache.velocity.runtime.parser.TokenMgrError: Lexical error at line 121, column 17. Encountered: <EOF> after : ""
5438 [WrapperSimpleAppMain] INFO org.codehaus.plexus.notification.notifier.Notifier:mail - The from mailbox is not configured, will use the nag email address from the project.
5438 [WrapperSimpleAppMain] INFO org.codehaus.plexus.notification.notifier.Notifier:mail - From name: Continuum
5438 [WrapperSimpleAppMain] INFO org.codehaus.plexus.notification.notifier.Notifier:mail - Build host name: uscus-build2
5563 [WrapperSimpleAppMain] INFO org.codehaus.plexus.notification.RecipientSource - To override address is not configured, will use the nag email address from the project.
5578 [WrapperSimpleAppMain] INFO org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - Starting task executor, thread name 'build-project'.
5578 [WrapperSimpleAppMain] INFO org.codehaus.plexus.PlexusContainer - Loading on start [role,roleHint]: [org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor,check-out-project]
5578 [WrapperSimpleAppMain] INFO org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:check-out-project - Starting task executor, thread name 'check-out-project'.
2151003 [scheduler1_Worker-8] INFO org.apache.maven.continuum.build.settings.SchedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
2151112 [scheduler1_Worker-8] INFO org.apache.maven.continuum.store.ContinuumStore:jdo - nb result : 3
5750995 [scheduler1_Worker-7] INFO org.apache.maven.continuum.build.settings.SchedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
5750995 [scheduler1_Worker-7] INFO org.apache.maven.continuum.store.ContinuumStore:jdo - nb result : 3
9351007 [scheduler1_Worker-13] INFO org.apache.maven.continuum.build.settings.SchedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
9351007 [scheduler1_Worker-13] INFO org.apache.maven.continuum.store.ContinuumStore:jdo - nb result : 3
12950997 [scheduler1_Worker-11] INFO org.apache.maven.continuum.build.settings.SchedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
12950997 [scheduler1_Worker-11] INFO org.apache.maven.continuum.store.ContinuumStore:jdo - nb result : 3
16550995 [scheduler1_Worker-8] INFO org.apache.maven.continuum.build.settings.SchedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
16550995 [scheduler1_Worker-8] INFO org.apache.maven.continuum.store.ContinuumStore:jdo - nb result : 3

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dan Tran added a comment -

Run continuum using command line, got more info. This is a shell build

jvm 1 | [INFO] The application server has started.
jvm 1 | 2005-12-19 10:00:00,013 [scheduler1_Worker-3] INFO SchedulesActivato
r - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
jvm 1 | 2005-12-19 10:00:00,075 [scheduler1_Worker-3] INFO ContinuumStore:jd
o - nb result : 3
jvm 1 | Dec 19, 2005 10:00:00 AM org.quartz.core.JobRunShell run
jvm 1 | SEVERE: Job DEFAULT.DEFAULT_SCHEDULE threw an unhandled Exception:
jvm 1 | java.lang.NullPointerException
jvm 1 | at org.apache.maven.continuum.DefaultContinuum.buildProjects(Def
aultContinuum.java:368)
jvm 1 | at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execut
e(ContinuumBuildJob.java:66)
jvm 1 | at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
jvm 1 | at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThre
adPool.java:516)
jvm 1 | Dec 19, 2005 10:00:00 AM org.quartz.core.ErrorLogger schedulerError
jvm 1 | SEVERE: Job (DEFAULT.DEFAULT_SCHEDULE threw an exception.
jvm 1 | org.quartz.SchedulerException: Job threw an unhandled exception. [See
nested exception: java.lang.NullPointerException]
jvm 1 | at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
jvm 1 | at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThre
adPool.java:516)
jvm 1 | * Nested Exception (Underlying Cause) ---------------
jvm 1 | java.lang.NullPointerException
jvm 1 | at org.apache.maven.continuum.DefaultContinuum.buildProjects(Def
aultContinuum.java:368)
jvm 1 | at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execut
e(ContinuumBuildJob.java:66)
jvm 1 | at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
jvm 1 | at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThre
adPool.java:516)

Show
Dan Tran added a comment - Run continuum using command line, got more info. This is a shell build jvm 1 | [INFO] The application server has started. jvm 1 | 2005-12-19 10:00:00,013 [scheduler1_Worker-3] INFO SchedulesActivato r - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)... jvm 1 | 2005-12-19 10:00:00,075 [scheduler1_Worker-3] INFO ContinuumStore:jd o - nb result : 3 jvm 1 | Dec 19, 2005 10:00:00 AM org.quartz.core.JobRunShell run jvm 1 | SEVERE: Job DEFAULT.DEFAULT_SCHEDULE threw an unhandled Exception: jvm 1 | java.lang.NullPointerException jvm 1 | at org.apache.maven.continuum.DefaultContinuum.buildProjects(Def aultContinuum.java:368) jvm 1 | at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execut e(ContinuumBuildJob.java:66) jvm 1 | at org.quartz.core.JobRunShell.run(JobRunShell.java:191) jvm 1 | at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThre adPool.java:516) jvm 1 | Dec 19, 2005 10:00:00 AM org.quartz.core.ErrorLogger schedulerError jvm 1 | SEVERE: Job (DEFAULT.DEFAULT_SCHEDULE threw an exception. jvm 1 | org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.NullPointerException] jvm 1 | at org.quartz.core.JobRunShell.run(JobRunShell.java:202) jvm 1 | at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThre adPool.java:516) jvm 1 | * Nested Exception (Underlying Cause) --------------- jvm 1 | java.lang.NullPointerException jvm 1 | at org.apache.maven.continuum.DefaultContinuum.buildProjects(Def aultContinuum.java:368) jvm 1 | at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execut e(ContinuumBuildJob.java:66) jvm 1 | at org.quartz.core.JobRunShell.run(JobRunShell.java:191) jvm 1 | at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThre adPool.java:516)
Hide
Permalink
Dan Tran added a comment -

Evenisse found the root cause

<evenisse> dantran: i seems an error when several projects doesn't use the schedule that run
<dantran> ummm, what does it mean? -)
<dantran> hang on, let me check my setup again
<dantran> i have a schedules that expires 2099
<dantran> practically, its never expires
<evenisse> do you have more than one schedule?
<dantran> but each of my projects does bind to a scheduler
<evenisse> it seems that if a project use scheduler A and an other project use scheduler B, NPE appears
<dantran> ic
<dantran> so it is a bug, not user error right?
<evenisse> yes

Show
Dan Tran added a comment - Evenisse found the root cause <evenisse> dantran: i seems an error when several projects doesn't use the schedule that run <dantran> ummm, what does it mean? -) <dantran> hang on, let me check my setup again <dantran> i have a schedules that expires 2099 <dantran> practically, its never expires <evenisse> do you have more than one schedule? <dantran> but each of my projects does bind to a scheduler <evenisse> it seems that if a project use scheduler A and an other project use scheduler B, NPE appears <dantran> ic <dantran> so it is a bug, not user error right? <evenisse> yes
Hide
Permalink
Dan Tran added a comment -

More conversation with Evenisse

<evenisse> the workaround is to use the same schedule for all projects
<evenisse> or write a patch for DefaultContinuum and use patched version
<dantran> does this bug already in 1.0.1?
<evenisse> i don't think, introduce by performance fix
<evenisse> it's very simple to fix
<dantran> evenisse, ok i will look into it
<evenisse> it just a test to do line 368 in DefaultContinuum

Show
Dan Tran added a comment - More conversation with Evenisse <evenisse> the workaround is to use the same schedule for all projects <evenisse> or write a patch for DefaultContinuum and use patched version <dantran> does this bug already in 1.0.1? <evenisse> i don't think, introduce by performance fix <evenisse> it's very simple to fix <dantran> evenisse, ok i will look into it <evenisse> it just a test to do line 368 in DefaultContinuum
Hide
Permalink
Emmanuel Venisse added a comment -

Applied. Thanks.

Show
Emmanuel Venisse added a comment - Applied. Thanks.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.