Re: Severe Bug in CronTimeTrigger

[Ulrich Mayring]

Thomas Kiesgen wrote:

Problem is, that on Dec 31 the getTimeAfter method returns a value in the
past
=> consequence in our scenario: trigger is executed again and again leading
to OutOfMemory-Error for the running app ;-((

I can confirm this, our production system simply stopped its service.

We did not have an out of memory error, because we caught the error condition (*tap on my shoulder*) and wrote a line to the logfile. Alas, we ran out of disk space, because the logfiles became so large :(

cheers,

Ulrich




--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>