> > Freeze in terms of minutes. But sorry, I haven't timed it yet. I stumbled across my issue again and checked the logs and the "freeze" is apparently 522 seconds:
09:31:41.124 INFO [http-8080-exec-8] lift [Slf4jLogger.scala:110] - Service req uest (GET) /mobile/mypage/ took 522397 Milliseconds I can also confirm that CPU is 99% idle. > > Is anybody actually using Tomcat and Comet together with Lift? Or is > > this oil and water? > > http://much4.usis Tomcat and Lift and has been running flawlessly for > nearly 2 years. Excellent news... I enabled NIO on Tomcat thinking that it will help, but still experiencing symptoms. Since I never saw symptoms with Jetty, I wondered if there were tips on configuring Tomcat for Lift. Alas, doesn't sound like that would be the problem. > Based on the other thread, you have a logic error in your Comet render > method. The application server is not freezing, the page is taking a long > time to render and it's taking a long time to render because it's waiting > for the comet component to render itself. If the behavior differs between > Jetty and Tomcat, it's likely that you have some sort of deadlock in your > code that's triggered based on the timing that you get out of Tomcat. It's > not a Lift thing. BTW... I'm actually not 100% convinced my "freeze" problem is related to Comet. I actually am experiencing the "freeze" pulling up a non- comet page. I can confirm that the freeze is not related to the database because each database query is coming pack in less than 10 ms. Can I also assume that Browser choice is irrelevent? Most of my development testing was with Chrome, but now I am using IE (6 and 8) in my testing. That shouldn't matter, right? -- 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.
