Re: DO NOT REPLY [Bug 28383] - [cron] OutOfMemoryError

[Jorg Heymans <jh...@domek.be>]

Antonio,

Can you elaborate on why i was getting all these exceptions? Is this 
predefined behaviour?

bugzilla@apache.org wrote:

> 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
> 
> agallardo@agsoftware.dnsalias.com changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|ASSIGNED                    |RESOLVED
>          Resolution|                            |FIXED
> 
> 
> 
> ------- Additional Comments From agallardo@agsoftware.dnsalias.com  2004-07-11 19:22 -------
> Tested. I already run the suggested sample and after 100 iterations it does not
> throws a OutOfMemoryError (OOME).
> 
> I will close the bug, please cross check. Perhaps it was fixed in the lib update
> or in a particular case the concurrent threads eats the memory. In the last case
> this is not a cocoon problem, a new scheduling need to be defined.
> 

Re: DO NOT REPLY [Bug 28383] - [cron] OutOfMemoryError

[Antonio Gallardo <ag...@agssa.net>]

Jorg Heymans dijo:
> Antonio,
>
> Can you elaborate on why i was getting all these exceptions? Is this
> predefined behaviour?

ou are right, the sample is broken. All in all, this is OT to solve the
bug. The problem was an OutOfMemory Error.

I am not sure why the source resolver in this case does not process the
requested URI. I think Reinhard or Giacomo can tell us why the sample is
broken and perhaps fix it.

I saw the sample is being broken at line 83:
http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/blocks/cron/java/org/apache/cocoon/components/cron/TestCronJob.java?annotate=1.8

BTW, I think Carsten fixed the bug in Revision 1.7:

http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/blocks/cron/java/org/apache/cocoon/components/cron/TestCronJob.java

Because if the resources does not get released then this can be the source
of the OutOfMemoryError.

Anyway, the cron job runned 100 iterations and no signs of eating memory.

Best Regards,

Antonio Gallardo.