[Webware-discuss] RE:

[Geoffrey T. <gta...@na...>]

The Ids section is the last part of the exception report unless you have
IncludeFancyTracebacks set to true, in which case a section with the title
"Fancy Traceback" comes after it.  Do you have IncludeFancyTracebacks set to
true, and if so, are you in fact seing the "Fancy Traceback" section?  Maybe
it's hanging in the code that generates the fancy traceback.
 
Also, does this fail with the standard Examples/Error servlet or only with a
servlet you wrote yourself?

- Geoff 

-----Original Message-----
From: Hancock, David (DHANCOCK) [mailto:DHA...@ar...]
Sent: Friday, April 26, 2002 2:23 PM
To: Geoffrey Talvola; 'web...@li...'
Subject: 


I first noticed this problem using IE-on-Windows.  I also see the problem in
several other client situations (these are all on Linux):
 
1. Using a Python script with urllib.py
2. Using wget
3. Using Netscape on Linux
 
Number 3 gives the most status information:  The error page displays, right
down to the uid/gid/etc. information, and the status bar states "12K read
(stalled)" and the "wait cursor" (the little wristwatch) displays until I
press Stop, at which point the status bar states "Document done."  At the
end of the page, then, is a horizontal rule, followed by "Transfer
interrupted!" in bold.
 
Now that I see what Netscape on Linux shows, there may be a clue.  Is there
supposed to be more error information AFTER the list of uid/gid/pid, etc.
The last think I see is 'getuid  500' (500 is the nobody user on my box).
If there's more information being collected, perhaps that's where the hang
is.

Cheers! 
-- 
David Hancock | dha...@ar... | 410-266-4384 

-----Original Message-----
From: Geoffrey Talvola [mailto:gta...@na...] 
Sent: Friday, April 26, 2002 1:02 PM
To: 'Hancock, David (DHANCOCK)'; 'web...@li...'
Subject: RE: [Webware-discuss] WebKit Error traceback pages don't close th
eir connection?


OK.  It doesn't happen here at work on Windows boxes, but I can try it this
weekend on my linux box at home.
 
Have you by any chance tried other clients beside IE-on-Windows?  I'll only
be able to test it with Linux browsers at home.
 
- Geoff 

-----Original Message-----
From: Hancock, David (DHANCOCK) [mailto:DHA...@ar...]
Sent: Friday, April 26, 2002 10:28 AM
To: Geoffrey Talvola; 'web...@li...'
Subject: RE: [Webware-discuss] WebKit Error traceback pages don't close th
eir connection?


Oops--sorry for incomplete information earlier.
 
OS: Linux (RedHat 6. b 2 distribution)
mod_webkit adapter
Python 2.2
Webware 0.7 (released, nothing newer from CVS)
NOT configured to email error reports
 
Cheers! 
-- 
David Hancock | dha...@ar... | 410-266-4384 

-----Original Message-----
From: Geoffrey Talvola [mailto:gta...@na...] 
Sent: Friday, April 26, 2002 10:19 AM
To: 'Hancock, David (DHANCOCK)'; 'web...@li...'
Subject: RE: [Webware-discuss] WebKit Error traceback pages don't close th
eir connection?


Which OS, adapter, Python version, and Webware version?  It it configured to
send email or not?
 
It doesn't happen to me, and like you, I get a lot of error pages :-)

- Geoff 

-----Original Message-----
From: Hancock, David (DHANCOCK) [mailto:DHA...@ar...]
Sent: Thursday, April 25, 2002 10:56 PM
To: 'web...@li...'
Subject: [Webware-discuss] WebKit Error traceback pages don't close their
connection?



When I get an error traceback page (it happens a lot, I make a lot of
mistakes), it seems like the HTTP connection doesn't get closed.  The
symptoms I see are that the traceback page loads, down to the end (I think),
where the IDs print, but the IE "globe" keeps spinning until I press the
Stop button on the browser.

When I request the /Examples/Error servlet via urllib in a Python script, it
hangs at the point of retrieving the page. If I press Ctrl-C, there's
nothing in the output file.

Any words of advice about what's going on and how I could fix it?  I'm
trying to write a cheesy automatic test for a servlet page that will simply
look for the presence of the traceback.  What I'm doing as a workaround is
assuming that no page will take more than 30 seconds to load (browser and
servlet on the same network), and handling an alarm if the timeout is
exceeded.

I appreciate any advice or pointers to information you can provide. 

Thanks.  By the way, the fancy traceback is a great boon for us--much easier
than finding and tailing a logfile. 

Cheers! 
-- 
David Hancock | dha...@ar... | 410-266-4384