Thanks for the reply, David!
I finally realized my problem is that I was compiling against the scala
2.7.3 library instead of 2.7.7 as I thought. When I use the newer lib, the
exception apparently goes away.
Regardless, what would be a good replacement for the scala actors library?
Thanks,
On Tue, Jan 19, 2010 at 11:58 PM, Yu-Shan Fung ambivale...@gmail.comwrote:
Thanks for the reply, David!
I finally realized my problem is that I was compiling against the scala
2.7.3 library instead of 2.7.7 as I thought. When I use the newer lib, the
exception apparently goes away.
Scala
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?
Thanks for the reply, Marius. Where can I get the 1.1 or 2.0 snapshot?
I'm not doing any scheduling myself. I just created a bunch of Future's, and
then call Futures.awaitAll. But my understanding is that Future is
implemented with Actor's.
val fResults = ids.map { id =
Howdy,
The short (and not politically popular) answer is that Scala's Actor
implementation is generally fragile and often broken. Lift made the painful
switch away from Scala Actors 4 or so months ago for this reason.
If you can put together a simple example of the failure (basically something
