> Can you define "freeze"?  Is that the Java process stops for a short period
> of time (~1 second)?  A long period of time (many minutes)?  Until you
> restart the Java process?  What does the CPU utilization look like?  Is the
> freezing for a single client/browser or all of them?

Freeze in terms of minutes.  But sorry, I haven't timed it yet.

I just posted a symptom here:  
http://groups.google.com/group/liftweb/browse_thread/thread/1d91ce365ed22216#

I decided to drill into my issue in more detail to try and find an
error message, stack trace, memory issue, CPU consumption -- anything
that might give me a hint.  Alas, the closest thing I have is the
FIXME comet timeout message.

I'd like to add that the code works some of the time (so I know that I
don't have a syntax error).  When it doesn't work, it is seemingly
random.  Not necessarily failing due to high load.  And actually, I am
the only one hitting the server (with perhaps two browser windows at
the most) right now.  So, it isn't like I have hundreds of users...


Is anybody actually using Tomcat and Comet together with Lift?  Or is
this oil and water?

Note that I am not using APR.  I don't think I am using NIO.  And I do
have compression turned on.  But 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 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.

Reply via email to