cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Romayev <roma...@yahoo.com>
Subject Re: TestCronJob
Date Sat, 05 Jun 2004 13:41:37 GMT
Hi Jeremy,

Thanks for the info.  

How "heavy" is your pipeline?  I found that pipelines
with many xslt transformations tend to fail quicker. 
For a simple pipeline to fail I would need to run it
every 5 seconds for about an hour.

Thanks,
-Alex

--- Jeremy Quinn <jeremy@media.demon.co.uk> wrote:
> Hi Alex
> 
> I have had this one running every 10 minutes for a
> day without memory 
> problems:
> 
> <trigger name="test-reminders"
> 
>
target="org.apache.cocoon.components.cron.CronJob/reminder"
> 	concurrent-runs="false">
> 	<minutes>*/10</minutes>
> 	<hours>*</hours>
> 	<days>*</days>
> 	<months>*</months>
> 	<weekdays>?</weekdays>
> </trigger>
> 
> <component
>
class="org.apache.cocoon.components.cron.TestCronJob"
> 
> logger="cron.reminders" 
>
role="org.apache.cocoon.components.cron.CronJob/reminder">
> 	<msg>Reminder email sent</msg>
> 	<sleep>23000</sleep>
> 	<pipeline>moderate/reminders</pipeline>
> </component>
> 
> HTH
> 
> regards Jeremy
> 
> On 4 Jun 2004, at 20:41, Alex Romayev wrote:
> 
> > Hi Jeremy,
> >
> > I tried using cron a couple of months ago and ran
> into
> > the following problem:
> >
> >
>
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28383
> >
> > I'd like to know if it's just me or if this
> happens
> > for you as well.
> >
> > Cheers,
> > -Alex
> >
> > --- Jeremy Quinn <jeremy@media.demon.co.uk> wrote:
> >> Hi All
> >>
> >> I am playing with
> o.a.c.components.cron.TestCronJob.
> >>
> >> I am using it to call a pipeline once per day
> that
> >> runs a FlowScript
> >> that scours a database for jobs that need doing
> and
> >> sending out email
> >> reminders.
> >>
> >> The FlowScript calls one pipeline to generate the
> >> email body via
> >> 'cocoon.processPipelineTo' and another pipeline
> to
> >> generate the cron
> >> log written by TestCronJob via 'cocoon.sendPage'.
> >>
> >> It works really well, many thanks !!!!!!
> >>
> >>
> >> Before starting this, I was expecting to have to
> >> write my own CronJob,
> >> but I found that TestCronJob did everything I
> needed
> >> (call a pipeline,
> >> log the output).
> >>
> >> However, there is something I do not understand
> >> about TestCronJob.
> >>
> >> It sleeps after it has done the job, for a
> >> configurable amount of time.
> >>
> >> 	try {
> >> 		Thread.sleep(m_sleep);
> >> 	} catch (final InterruptedException ie) {
> >> 		//getLogger().error("CronJob " + name + "
> >> interrupted", ie);
> >> 	}
> >>
> >> Is it doing this because it is a test class and
> this
> >> is providing some
> >> kind of debug information, or is it doing it
> because
> >> this is something
> >> that a CronJob needs to do, and I would need to
> take
> >> care to set the
> >> sleep parameter appropriately.
> >>
> >> Thanks for any suggestions
> >>
> >> regards Jeremy
> >>
> >>
> >
> >> ATTACHMENT part 2 application/pkcs7-signature
> > name=smime.p7s
> >
> >
> 

> ATTACHMENT part 2 application/pkcs7-signature
name=smime.p7s



Mime
View raw message