Re: Notification when HTTP client aborted connection?
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 webserver, we want to get notified. This way, we can abort the database connection, so the database isn't being used to run unnecessary searches. First, is there a facility in the API for a servlet to set up a listener, so the servlets gets notified when the servlet container has lost the connection? Secondly, is anyone aware of any webserver implementation which triggers the notification? It seems that this would be an obvious kind of feature, but doesn't seme to be implemented. I also asked on the Sun Java Servlet forum, but no one seems to have any idea. Thanks Steve __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Sorry for the flaky post
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
Architectural question
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 threads and never return from the service method. While this does appear to work (the client gets its data), we're also finding that Apache does not always let the mod_jk connection go when the client closes its connection to Apache asynchronously, so that the feed goes on and on even when no one is listening. Eventually there are serious resource issues. My questions are these: 1. Is this expected behavior in mod_jk, that is, could it be that mod_jk is waiting for the servlet to exit its service method before letting go its connection to Tomcat, even though the client has long since closed its connection to Apache? 2. If it is expected behavior, is there a simple workaround? (We do send a second request to close the feed, although we can't count on this happening in the case of network failure.) 3. Are we totally out of our minds to be architecting a system this way? Thanks. David -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Configuring log files in Tomcat 4.1
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 help in this. Does anyone have any specifics on how I can configure log files and redirect System.out and System.err messages? I'm using Tomcat 4.1.12. Thanks. David -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
