> > Jetty seems to do questionable things with filehandles, opening > > multiple copies of the same template file and keeping them open too > > long. Setting ulimit "fixes" the issue of "Too many open files" > > exceptions & failed requests, but it still seems like at most > > templates should need 1 access to check mtime. Not really a lift > > issue, and not a deal breaker for us to switch to a different servlet > > container, but I am curious to see what the eventual solution for > > comet performance is. > > If you can put together a reproducible case on this, we'll see what we can > do to close stuff that Jetty hands us more explicitly.
I'm a total Lift and Scala newbie, but file-handle problems and last- modified checks remind me of this bug in Facelets: https://facelets.dev.java.net/issues/show_bug.cgi?id=278 It looks like ResourceServer.scala may be hitting the same problem between the findResourceInClasspath and calcLastModified methods, but again - total newbie - so take that with a boulder sized grain of salt. -- Nathan -- 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=en.
