You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2004/07/11 19:00:23 UTC
DO NOT REPLY [Bug 28383] -
[cron] OutOfMemoryError
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28383>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28383
[cron] OutOfMemoryError
------- Additional Comments From jh@domek.be 2004-07-11 17:00 -------
Just playing with this ...
- I enabled the cron block and samples.
- I enabled the trigger and modified it as described below
I get
INFO (2004-07-11) 18:54.06:013 [cron] Unknown-thread/QuartzJobExecutor:
Scheduling cron job named 'test-job2'
INFO (2004-07-11) 18:54.06:013 [cron.test] Unknown-thread/TestCronJob:
CronJob test-job2 launched at Sun Jul 11 18:54:06 CEST 2004 with message 'I'm
here' and sleep timeout of 10000ms
ERROR (2004-07-11) 18:54.06:013 [cron] Unknown-thread/QuartzJobExecutor:
Cron job name 'test-job2 died.
org.apache.avalon.framework.CascadingRuntimeException: CronJob test-job2 raised
an exception
at org.apache.cocoon.components.cron.TestCronJob.execute(TestCronJob.java:100)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.avalon.excalibur.component.ComponentProxyGenerator$ComponentInvocationHandler.invoke(ComponentProxyGenerator.java:143)
at $Proxy1.execute(Unknown Source)
at
org.apache.cocoon.components.cron.QuartzJobExecutor.execute(QuartzJobExecutor.java:109)
at org.quartz.core.JobRunShell.run(JobRunShell.java:188)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.UnsupportedOperationException
at
org.apache.cocoon.environment.background.BackgroundEnvironment$NullProcessor.getContext(BackgroundEnvironment.java:164)
at
org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:55)
at
org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:70)
at org.apache.cocoon.components.cron.TestCronJob.execute(TestCronJob.java:83)
... 9 more
What's the deal with this nullprocessor? (cocoon 2.1HEAD from a few minutes ago)