I have some questions... At 03:02 PM 10/22/01 -0400, Clark C . Evans wrote: >About two months ago, I was having problems where someone >started to upload a file and canceled half way through. >This causes the webware server to abort and stop processing >clients. I have a similar problem...
What OS are you using, and which adapter are you using? Does it make a difference if you switch to the CGI adapter? Does file uploading still cause Webware to abort even with the latest release? Is it reliably reproducible, for example with the FileUpload example servlet? Does the WebKit process actually exit? Or is it still running but unable to handle requests? If the latter, does its CPU usage shoot up, or is it idle? >Suppose I have two servlets A and B. Servlet A executes a >long-running query against PostgreSQL (1-2 seconds) and returns >quite a bit of information. Servlet B is much smaller. >Also suppose that I have a pipe with some pretty decent >latency. Now. Suppose a user using IE Explorer or Netscape >on both Windows or Macintosh hits servlet B. Immediately after >clicking on a link for this servlet (as the page starts to return) >they click on servlet A. Bang. No logs, nothing. The >back-end webware process crashes. I seem to remember someone else having problems with Webware crashing due to a bug in the PostgreSQL module. They upgraded to a newer version of the PostgreSQL Python module and the crashes went away. You might want to look in the mail list archives for more information about that. >I have two questions: > > 1. How do I setup a process so that when webware dies > it auto-restarts? This is a temporary fix needed > for this and other problems which may also have the > same symptoms. On Unix, there's Monitor.py. I haven't ever used it though. > 2. How do I better debug this bugger? Sorry, I've been > working on applicaiton logic for some time, so I don't > have the nitty-gritty details of Webware debugging > in my pocket. With this type of problem, I usually try to put in lots of logging so I can figure out where it crashed. You can log the thread ID by printing out threading.currentThread().getName() which can be helpful if you're trying to debug a problem that only wedges/crashes one thread. >Also. I just put into "production" the recent CVS snapshot, >the same problem occurs. > >Thanks! -- - Geoff Talvola [EMAIL PROTECTED] _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
