What version of Lift are you using? Please supply the entire stack trace.
If you have some code that reproduces the problem, that would be helpful. It looks like the db connection is getting closed manually and then when the auto-close tries to close it again, the exception is thrown. On Dec 13, 2008 6:46 AM, "Michael" <[email protected]> wrote: I have a CometActor that crashes after rendering and then re-rendering after it responds to a message. The stack trace that gets printed looks like: ERROR - The ActorWatcher restarted foo.comet.myac...@1e6ee98 because scala.MatchError: None scala.MatchError: None at net.liftweb.mapper.DB$.releaseConnectionNamed(DB.scala:127) at net.liftweb.mapper.DB$.use(DB.scala:283) at net.liftweb.mapper.DB$$anon$1.net$liftweb$mapper$DB$$anon$ $doWith(DB.scala:109) at net.liftweb.mapper.DB$$anon$1.apply(DB.scala:112) at net.liftweb.http.S$.net$liftweb$http$S$$doAround(S.scala: 368) I tried putting the following in the lowPriority method: override def lowPriority : PartialFunction[Any, Unit] = { case NormalMessage(a,u) => { doStuff(a,u) reRender(false) } case None => { println("None?") } case s => { println("Other " + s.toString) } } Nothing gets printed out before the stack trace. After the stack trace I see Other <function> This repeats periodically, but the CometActor is dead. Is there something bad about using a Mapper object with Actors, or is there something else going on here? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
