Steve Parkinson wrote:
We have some servlets which may potentially create
long-lived database searches, data mining, etc. If the
user is willing to wait for the servlet to complete,
everything is good, but if they press 'stop', visit
another page, or otherwise close the connection to the
Hit the send button before I could do what I wanted to do - sorry.
d
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
We're running Apache 1.3 with Tomcat 3.2 in an application at work and
have been seeing some strange behavior. What we've got is this: one of
our servlets, when requested, opens a real-time feed that sends a
neverending stream of data to the client. We basically hijack one of
the Tomcat
I get an annoying SSL warning in catalina.out on every request if the
client is not authenticated by certificate, which in our application
means every request. I would love to configure logging to (a) not log
this warning message and (b) call catalina.out something else. The docs
aren't much
