You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Kevan Miller <ke...@gmail.com> on 2007/03/02 04:35:55 UTC

[private] Re: Timer already canceled

On Mar 1, 2007, at 11:51 AM, Spotts, Joel ((ISS Atlanta)) wrote:

> Thanks for the suggestions. Sorry I forgot to mention I am running
> version 1.1.1. I tried increasing the heap size to 378 MB, but did not
> help. I am attaching the full log file. One thing to note is that our
> code creates a Timer class which runs into an exception as can be  
> seen.
> This exception is caught in out code and spit to the log file. Its  
> hard
> to imagine that is connected, since they are two different Timer
> instances, but it does seem interesting that the Timer already  
> canceled
> exception occurs right after our own exception in a Timer.
>
> Another thing to note is that geronimo doesn't just quit after the
> exception, it keeps on trucking, but the CPU spikes to 100% and for  
> all
> intents and purposes, geronimo is dead.

Hi Yoel,
Strange. Possible that you can set me up to recreate this?

Possible that you can inhibit your timer error? Curious if the  
problem still occurs...

What JRE are you using?

--kevan