I'd recommend using Lisft 1.1-SNAPSHOT or 2.0-SNAPSHOT You stacktrace doesn't indicate anything related with Lift, so are you using Java's scheduler, or are you using actors? Lift's ActorPing and actors is a good way of doing scheduling. So can you elaborate on how are you doing the scheduling?
Br's, Marius On Jan 19, 8:04 am, Yu-Shan Fung <[email protected]> wrote: > Hi All, > > I have a lift app, where one of the functions performs sub-computations > (including network operations) in parallel via future(s) & Futures.awaitAll. > It runs fine on the first request, but subsequent requests throws a > IllegalStateException: > > Exception in thread "Thread-30" java.lang.IllegalStateException: Timer > already cancelled. > at java.util.Timer.sched(Timer.java:376) > at java.util.Timer.schedule(Timer.java:192) > at scala.actors.Futures$.awaitAll(Future.scala:76) > at MyWorker.run(MyWorker.scala:20) > at java.lang.Thread.run(Thread.java:636) > > I dug up more documentation and it looks like this exception indicates an > attempt to schedule a task on a timer that has already been cancelled > (associated daemon thread terminated?). Any idea why, or if I'm doing > something wrong? > > In case it matters, I'm running Scala code runner version 2.7.7.final, > Liftweb 1.0, Jetty 6.1.22. > > Any tips/pointers would be appreciated. Thanks! > Yu-Shan > > -- > “When nothing seems to help, I go look at a stonecutter hammering away at > his rock perhaps a hundred times without as much as a crack showing in it. > Yet at the hundred and first blow it will split in two, and I know it was > not that blow that did it, but all that had gone before.” — Jacob Riis
-- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
