cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Quoin Developers <>
Subject bug? dupliate triggers/jobs with cron block
Date Wed, 01 Feb 2006 00:40:16 GMT
I'm using the cron block to launch a CronJob. I'm seeing two instances
of my CronJob created - one with a NullLogger, and one that logs to
the standard cocoon log (that was hard to track down!).

Enable logging is being called from the same place in each instance:

        at org.apache.avalon.framework.container.ContainerUtil.enableLogging(
        at org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(
        at org.apache.avalon.excalibur.component.DefaultComponentHandler.doGet(
        at org.apache.avalon.excalibur.component.ComponentHandler.get(
        at org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(
        at org.apache.cocoon.components.CocoonComponentManager.lookup(
        at org.apache.avalon.framework.service.WrapperServiceManager.lookup(
        at org.apache.cocoon.components.cron.QuartzJobExecutor.execute(
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$

It looks like I'm getting two instances of the QuartzJobExecutor from
my trigger.

Has anyone seen this before? Any suggestions what I'm doing wrong, or
is this a bug?

There is nothing particular remarkable about the component
declarations for the jobs or for the cron/trigger declarations (they
are much like the example from the cron block).

Thanks in advance, as I'm starting to pull my hair out on this one.

Eric Meyer

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message