I am able to duplicate this error. I was concerned that it might be the result of my Loc changes, so I just rebuilt Lift without the patches associated with that change and reproduced the problem again.
Here are the conditions under which I'm able to reproduce the failure: 1) load a page where the snippets are managed by a StatefulSnippet 2) some page elements (in my case select boxes) have their values update by AJAX in response to user events. This appears to work normally. 3) upon submission of the form on the page, the page is re-rendered. Logging in the submission function indicates that it is never called. 4) if I fill in the form again and resubmit after the initial failure, the form submit behaves properly. 5) I believe I've seen at least one instance (though I can't reliably reproduce this) where just a normal AJAX call (modifying one of the select boxes) caused the entire page to reload. Kris Kris On Tue, Nov 17, 2009 at 4:07 PM, O'Rorke Paul <p...@ororke.com> wrote: > Not in a place where I can really debug this right now but I'm curious > whether anybody else has seen this and knows the solution... > > since rebuilding a day or two ago with no recent code or other changes: > every second time I go to click on an ajax checkbox or select widget, > I get effectively no response. > actually, it looks like there is a very quick spinning wheel (almost > imperceptible) but the page doesn't get repainted and the database > does not change. > If I use another operation that is non ajax (going in and editing an > item and doing old fashioned get / posts) everything works fine after > that (one time). > Or if I reload the page then if I use an ajax widget after reloading > ajax works (once). > > This is with 2.7.5 Scala and Lift 1.1-SNAPSHOT. > > Perhaps not coincidentally, I am getting "Multiple versions of scala > libraries detected!" warnings and have not yet figured out how to get > rid of them. > I don't see another version of Scala in my pom or eclipse maven > dependency graph and have been going around nuking old copies of scala > but to no avail as yet. > > Another odd thing that is now happening is that when I shutdown with a > control C in the terminal window, I get the following error: > >> INFO - Service request (GET) /ajax_request/liftAjax.js took 2 >> Milliseconds >> ^C2009-11-16 15:29:01.634::INFO: Shutdown hook executing >> 2009-11-16 15:29:02.249::INFO: Shutdown hook complete >> [INFO] Jetty server exiting. >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD SUCCESSFUL >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 33 minutes 4 seconds >> [INFO] Finished at: Mon Nov 16 15:29:02 PST 2009 >> [INFO] Final Memory: 23M/257M >> [INFO] >> ------------------------------------------------------------------------ >> ERROR - Couldn't start SessionMaster ping >> net.liftweb.util.ActorPingException: net.liftweb.http.SessionMaster >> $checkandpur...@1cab4a5 could not be scheduled on >> net.liftweb.http.sessionmast...@119c2af >> at net.liftweb.util.ActorPing$.schedule(ActorPing.scala:54) >> at net.liftweb.http.SessionMaster$.net$liftweb$http$SessionMaster$ >> $doPing(LiftSession.scala:187) >> at net.liftweb.http.SessionMaster$$anonfun$1.apply >> (LiftSession.scala:169) >> at net.liftweb.http.SessionMaster$$anonfun$1.apply >> (LiftSession.scala:135) >> at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala: >> 247) >> at net.liftweb.http.SessionMaster$.execTranslate(LiftSession.scala: >> 91) >> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor >> $SpecializedLiftActor$$processMailbox(LiftActor.scala:142) >> at net.liftweb.actor.SpecializedLiftActor$$anonfun$3$$anonfun$apply >> $1.apply(LiftActor.scala:109) >> at net.liftweb.actor.SpecializedLiftActor$$anonfun$3$$anonfun$apply >> $1.apply(LiftActor.scala:109) >> at net.liftweb.actor.LAScheduler$$anonfun$1$$anon$1$$anon$2.run >> (LiftActor.scala:37) >> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask >> (ThreadPoolExecutor.java:886) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run >> (ThreadPoolExecutor.java:908) >> at java.lang.Thread.run(Thread.java:637) >> Caused by: java.util.concurrent.RejectedExecutionException >> at java.util.concurrent.ThreadPoolExecutor >> $AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1760) >> at java.util.concurrent.ThreadPoolExecutor.reject >> (ThreadPoolExecutor.java:767) >> at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute >> (ScheduledThreadPoolExecutor.java:216) >> at java.util.concurrent.ScheduledThreadPoolExecutor.schedule >> (ScheduledThreadPoolExecutor.java:379) >> at java.util.concurrent.Executors >> $DelegatedScheduledExecutorService.schedule(Executors.java:654) >> at net.liftweb.util.ActorPing$.schedule(ActorPing.scala:52) >> ... 12 more >> > > Ideas / Suggestions for any of these issues (perhaps they are > related?) most welcome! > ---Paul O > > > > > -- > > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@googlegroups.com. > To unsubscribe from this group, send email to > liftweb+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=. > > > -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=.
