[Lift] Re: OOME in using CometActor

2009-09-16 Thread Atsuhiko Yamanaka
Hi, On Wed, Sep 16, 2009 at 11:50 PM, Atsuhiko Yamanaka wrote: > I'll try lower value, for example, 50 for maxPoolSize before going to the bed. > I'll look forward to the good result in the next morning. I got the good result. By setting maxPoolSize as 50, OOME had not appeared. With that sett

[Lift] Re: OOME in using CometActor

2009-09-16 Thread Atsuhiko Yamanaka
Hi, On Wed, Sep 16, 2009 at 11:36 PM, Erik Engbrecht wrote: > Yes, particularly maxPoolSize. Thank you for prompt reply. I'll try lower value, for example, 50 for maxPoolSize before going to the bed. I'll look forward to the good result in the next morning. Sincerely, -- Atsuhiko Yamanaka JCr

[Lift] Re: OOME in using CometActor

2009-09-16 Thread Erik Engbrecht
Yes, particularly maxPoolSize. On Wed, Sep 16, 2009 at 10:25 AM, Atsuhiko Yamanaka < atsuhiko.yaman...@gmail.com> wrote: > > Hi, > > On Wed, Sep 16, 2009 at 10:33 PM, Erik Engbrecht > wrote: > > The large number of VolatileTaskRefs is a consequence of your thread pool > > growth. Each worker th

[Lift] Re: OOME in using CometActor

2009-09-16 Thread Atsuhiko Yamanaka
Hi, On Wed, Sep 16, 2009 at 10:33 PM, Erik Engbrecht wrote: > The large number of VolatileTaskRefs is a consequence of your thread pool > growth.  Each worker thread maintains an array of VolatileTaskRef objects. > The VolatileTaskRef objects are reused rather than allocated for each task, > so

[Lift] Re: OOME in using CometActor

2009-09-16 Thread Erik Engbrecht
The large number of VolatileTaskRefs is a consequence of your thread pool growth. Each worker thread maintains an array of VolatileTaskRef objects. The VolatileTaskRef objects are reused rather than allocated for each task, so they will not be GC'd as long as the worker thread is alive. You can t

[Lift] Re: OOME in using CometActor

2009-09-16 Thread Derek Williams
I believe I ran into this before, to fix it I came up with this: package scala.actors object ActorTimerKiller { def kill { Actor.timer.cancel } } and then in my Boot.scala: LiftRules.unloadHooks.append(() => { ActorTimerKiller.kill } I also have Actor.clearSelf in my unloadHooks, b

[Lift] Re: OOME in using CometActor

2009-09-16 Thread David Pollak
On Wed, Sep 16, 2009 at 3:38 AM, Atsuhiko Yamanaka < atsuhiko.yaman...@gmail.com> wrote: > Hi, > > I have encountered OutOfMemory Exception in developing Liftweb app. > It seems it is related to CometActor(, or scala.actors.Actor) > At OOME timing, I have found 1,000,000 instances of > scala.acto