cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jorg Heymans ...@domek.be>
Subject Re: DO NOT REPLY [Bug 28383] - [cron] OutOfMemoryError
Date Sun, 11 Jul 2004 19:38:09 GMT
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.
> 


Mime
View raw message