Philippe, I got it going, and I might even understand why it failed :) I used SIXX to serialize some user data (a poor-man's access control list). Loading the "list" from SIXX output loads the data and the mutex; replacing the mutex with a new mutex seems to allow things to work. IIRC, this arises in Dolphin too. I have copied Masashi just in case that raises any alarms.
If I am correct about this, I sent the image crashing head on into a defective mutex, so the vm might have been correct to squawk about nothing being available to run. Thanks! Bill ________________________________________ From: [email protected] [[email protected]] On Behalf Of Schwab,Wilhelm K [[email protected]] Sent: Thursday, June 24, 2010 1:47 PM To: [email protected] Cc: [email protected] Subject: [Pharo-project] Seaside app crashing - does it sound familiar? Hello all, I am trying to pick up after a few months on a Seaside app. A lot has happened in that time, and I am not certain of its state, except to say that I recall seeing it display some pages. Now it's not working. At least some other Seaside apps are working, and going back to my 1.0 image, it is crashing with "scheduler could not find a runnable process." Are there any common mis-configurations or programming errors that can lead to that? I'll keep digging, but I wanted to post this just in case it's a known punishment for a common crime. Bill _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
