cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 28383] New: - [cron] OutOfMemoryError
Date Wed, 14 Apr 2004 15:52:10 GMT
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

           Summary: [cron] OutOfMemoryError
           Product: Cocoon 2
           Version: Current CVS 2.1
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: blocks
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: romayev@yahoo.com


Steps:

1. Uncomment the trigger in cocoon.xconf.
2. Change it to (so that it runs every 12 seconds and every minute):

            <trigger name="test-job2"
                 target="org.apache.cocoon.components.cron.CronJob/test"
                 concurrent-runs="true">
                <seconds>*/12</seconds>
                <minutes>*</minutes>
                <hours>*</hours>
                <days>?</days>
                <months>*</months>
                <weekdays>SUN-FRI</weekdays>
            </trigger>
3. Check the logs

Evenually it'll fail with OutOfMemoryError (for me it took about 30 runs)

Mime
View raw message