You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Olivier Lamy <ol...@accor.com> on 2005/12/21 14:44:50 UTC

RE : Errors in LOG

I have try it and the fix seems to be ok.
Thanks,
- Olivier

-----Message d'origine-----
De : Emmanuel Venisse [mailto:emmanuel@venisse.net] 
Envoyé : mercredi 21 décembre 2005 14:33
À : continuum-users@maven.apache.org
Objet : Re: Errors in LOG


it's a known bug when you have more than one schedule.

you can try with this jar :
http://beaver.codehaus.org/~evenisse/continuum-core-1.1-SNAPSHOT.jar

Put it in continuum/apps/continuum/lib
and remove old continuum-core jar

Let me know if it fix the problem.

Emmanuel

Ricardo de Souza Moura a écrit :
> I have had many errors in my log. Whenever I access the pages I get
> errors like that:
> 
> jvm 1    | 2005-12-21 10:37:19,992 [SocketListener0-1] ERROR 
> VelocityComponent              - RHS of #set statement is null.
Context 
> will not be modified. screens/Summary.vm [line 53, column 1]
> jvm 1    | 2005-12-21 10:37:19,992 [SocketListener0-1] ERROR 
> VelocityComponent              - RHS of #set statement is null.
Context 
> will not be modified. screens/Summary.vm [line 53, column 1]
> jvm 1    | 2005-12-21 10:37:20,007 [SocketListener0-1] ERROR 
> VelocityComponent              - RHS of #set statement is null.
Context 
> will not be modified. screens/Summary.vm [line 53, column 1]
> jvm 1    | 2005-12-21 10:37:20,007 [SocketListener0-1] ERROR 
> VelocityComponent              - RHS of #set statement is null.
Context 
> will not be modified. screens/Summary.vm [line 53, column 1]
> jvm 1    | 2005-12-21 10:37:20,007 [SocketListener0-1] ERROR 
> VelocityComponent              - RHS of #set statement is null.
Context 
> will not be modified. screens/Summary.vm [line 53, column 1]
> 
> 
> besides it I have had some problems with schedule. In spite of working
> well, every time that ir run, some errors appear in my log:
> 
> jvm 1    | Dec 21, 2005 10:40:01 AM org.quartz.core.JobRunShell run
> jvm 1    | SEVERE: Job DEFAULT.EVERY_5_MIN_SCHEDULE threw an unhandled

> Exception:
> jvm 1    | java.lang.NullPointerException
> jvm 1    |      at 
> org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultConti
> nuum.java:368)
> 
> jvm 1    |      at 
> org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(Continu
> umBuildJob.java:66)
> 
> jvm 1    |      at
org.quartz.core.JobRunShell.run(JobRunShell.java:191)
> jvm 1    |      at 
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.ja
> va:516)
> 
> jvm 1    | Dec 21, 2005 10:40:01 AM org.quartz.core.ErrorLogger 
> schedulerError
> jvm 1    | SEVERE: Job (DEFAULT.EVERY_5_MIN_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(SimpleThreadPool.ja
> va:516)
> 
> jvm 1    | * Nested Exception (Underlying Cause) ---------------
> jvm 1    | java.lang.NullPointerException
> jvm 1    |      at 
> org.apache.maven.continuum.DefaultContinuum.buildProjectsDefaultContin
> uum.java:3
> 
> 68)
> jvm 1    |      at 
> org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(Continu
> umBuildJob.java:66)
> 
> jvm 1    |      at
org.quartz.core.JobRunShell.run(JobRunShell.java:191)
> jvm 1    |      at 
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.ja
> va:516)
> 
> 
> My cron setup in schedule is:  0 0/5 * * * ?
> 
> Before the application server startup I had this error:
> 
> jvm 1    | 2005-12-21 10:35:30,744 [WrapperSimpleAppMain] ERROR 
> 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.  E
> ncountered: <EOF> after : ""
> 
> In spite of this problems, everything works well. How can I resolve 
> this ? Thanks !!!!
> 
> 
> 
> 
> 



This e-mail, any attachments and the information contained therein ("this message") are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited.
--------------------------------------------------------------------------------------------------------------
Ce message électronique et tous les fichiers joints ainsi que  les informations contenues dans ce message ( ci après "le message" ), sont confidentiels et destinés exclusivement à l'usage de la  personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci  de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites.
-------------------------------------------------------------------------------------------------------------


Re: RE : Errors in LOG

Posted by Laurent Forêt <la...@gmail.com>.
+1, OK for me too !

Laurent.

2005/12/21, Olivier Lamy <ol...@accor.com>:
>
> I have try it and the fix seems to be ok.
> Thanks,
> - Olivier
>
> -----Message d'origine-----
> De : Emmanuel Venisse [mailto:emmanuel@venisse.net]
> Envoyé : mercredi 21 décembre 2005 14:33
> À : continuum-users@maven.apache.org
> Objet : Re: Errors in LOG
>
>
> it's a known bug when you have more than one schedule.
>
> you can try with this jar :
> http://beaver.codehaus.org/~evenisse/continuum-core-1.1-SNAPSHOT.jar
>
> Put it in continuum/apps/continuum/lib
> and remove old continuum-core jar
>
> Let me know if it fix the problem.
>
> Emmanuel
>
> Ricardo de Souza Moura a écrit :
> > I have had many errors in my log. Whenever I access the pages I get
> > errors like that:
> >
> > jvm 1    | 2005-12-21 10:37:19,992 [SocketListener0-1] ERROR
> > VelocityComponent              - RHS of #set statement is null.
> Context
> > will not be modified. screens/Summary.vm [line 53, column 1]
> > jvm 1    | 2005-12-21 10:37:19,992 [SocketListener0-1] ERROR
> > VelocityComponent              - RHS of #set statement is null.
> Context
> > will not be modified. screens/Summary.vm [line 53, column 1]
> > jvm 1    | 2005-12-21 10:37:20,007 [SocketListener0-1] ERROR
> > VelocityComponent              - RHS of #set statement is null.
> Context
> > will not be modified. screens/Summary.vm [line 53, column 1]
> > jvm 1    | 2005-12-21 10:37:20,007 [SocketListener0-1] ERROR
> > VelocityComponent              - RHS of #set statement is null.
> Context
> > will not be modified. screens/Summary.vm [line 53, column 1]
> > jvm 1    | 2005-12-21 10:37:20,007 [SocketListener0-1] ERROR
> > VelocityComponent              - RHS of #set statement is null.
> Context
> > will not be modified. screens/Summary.vm [line 53, column 1]
> >
> >
> > besides it I have had some problems with schedule. In spite of working
> > well, every time that ir run, some errors appear in my log:
> >
> > jvm 1    | Dec 21, 2005 10:40:01 AM org.quartz.core.JobRunShell run
> > jvm 1    | SEVERE: Job DEFAULT.EVERY_5_MIN_SCHEDULE threw an unhandled
>
> > Exception:
> > jvm 1    | java.lang.NullPointerException
> > jvm 1    |      at
> > org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultConti
> > nuum.java:368)
> >
> > jvm 1    |      at
> > org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(Continu
> > umBuildJob.java:66)
> >
> > jvm 1    |      at
> org.quartz.core.JobRunShell.run(JobRunShell.java:191)
> > jvm 1    |      at
> > org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.ja
> > va:516)
> >
> > jvm 1    | Dec 21, 2005 10:40:01 AM org.quartz.core.ErrorLogger
> > schedulerError
> > jvm 1    | SEVERE: Job (DEFAULT.EVERY_5_MIN_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(SimpleThreadPool.ja
> > va:516)
> >
> > jvm 1    | * Nested Exception (Underlying Cause) ---------------
> > jvm 1    | java.lang.NullPointerException
> > jvm 1    |      at
> > org.apache.maven.continuum.DefaultContinuum.buildProjectsDefaultContin
> > uum.java:3
> >
> > 68)
> > jvm 1    |      at
> > org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(Continu
> > umBuildJob.java:66)
> >
> > jvm 1    |      at
> org.quartz.core.JobRunShell.run(JobRunShell.java:191)
> > jvm 1    |      at
> > org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.ja
> > va:516)
> >
> >
> > My cron setup in schedule is:  0 0/5 * * * ?
> >
> > Before the application server startup I had this error:
> >
> > jvm 1    | 2005-12-21 10:35:30,744 [WrapperSimpleAppMain] ERROR
> > 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.  E
> > ncountered: <EOF> after : ""
> >
> > In spite of this problems, everything works well. How can I resolve
> > this ? Thanks !!!!
> >
> >
> >
> >
> >
>
>
>
> This e-mail, any attachments and the information contained therein ("this
> message") are confidential and intended solely for the use of the
> addressee(s). If you have received this message in error please send it back
> to the sender and delete it. Unauthorized publication, use, dissemination or
> disclosure of this message, either in whole or in part is strictly
> prohibited.
>
> --------------------------------------------------------------------------------------------------------------
> Ce message électronique et tous les fichiers joints ainsi que  les
> informations contenues dans ce message ( ci après "le message" ), sont
> confidentiels et destinés exclusivement à l'usage de la  personne à laquelle
> ils sont adressés. Si vous avez reçu ce message par erreur, merci  de le
> renvoyer à son émetteur et de le détruire. Toutes diffusion, publication,
> totale ou partielle ou divulgation sous quelque forme que se soit non
> expressément autorisées de ce message, sont interdites.
>
> -------------------------------------------------------------------------------------------------------------
>
>