Bill Eldridge suggested using WebClip to see where in the output stream the
hang occurs, and that actually helped me find two things:
1. Without the WebClip webdebug proxy, the hang is right BEFORE
</body></html> at the end of the page. This is reliably true with or without
FancyTraceback turned on. It turns out that patience (like several minutes
of patience) results in the trailing close tags coming across the wire, and
the page is complete. (That's a bit too long to wait.)
2. Using the webdebug proxy, the page hangs and loads nothing (only the
request shows up in webdebug's menus) until about 300 seconds later, then
the whole page is loaded.
What I think this says is that the page is nearly completed and sent, and
only the last few bytes are "hanging" out there. When (supposition only)
some sort of timeout occurs, the rest of the bytes are sent out.
I'd tried webdebug at Bill's suggestion the other day, but stupidly tried to
proxy through 2021, not 2001, the default port.
Here's a netstat on the server machine "steady state" followed by while the
error page is wedged:
[dhancock@... dhancock]$ netstat -an | grep 9034
tcp 1 8640 127.0.0.1:9034 127.0.0.1:3483 CLOSE
tcp 0 0 127.0.0.1:9034 0.0.0.0:* LISTEN
[dhancock@... dhancock]$ netstat -an | grep 9034
tcp 1 0 127.0.0.1:9034 127.0.0.1:3491
CLOSE_WAIT
tcp 0 0 127.0.0.1:3491 127.0.0.1:9034
FIN_WAIT2
tcp 0 0 127.0.0.1:3490 127.0.0.1:9034
TIME_WAIT
tcp 0 0 127.0.0.1:3489 127.0.0.1:9034
TIME_WAIT
tcp 0 0 127.0.0.1:3488 127.0.0.1:9034
TIME_WAIT
tcp 0 0 127.0.0.1:9034 0.0.0.0:* LISTEN
[dhancock@... dhancock]$
I can't profess to understanding these states, but maybe this will ring a
bell with somebody.
Once the five minutes elapses, netstat says:
[dhancock@... dhancock]$ netstat -an | grep 9034
tcp 1 0 127.0.0.1:9034 127.0.0.1:3491
CLOSE_WAIT
tcp 0 0 127.0.0.1:3491 127.0.0.1:9034
FIN_WAIT2
tcp 0 0 127.0.0.1:9034 0.0.0.0:* LISTEN
[dhancock@... dhancock]$
Cheers!
--
David Hancock | dhancock@... | 410-266-4384
-----Original Message-----
From: Hancock, David (DHANCOCK) [mailto:DHANCOCK@...]
Sent: Wednesday, May 01, 2002 1:40 PM
To: 'Geoffrey Talvola'; 'webware-discuss@...'
Subject: RE: [Webware-discuss] WebKit Error traceback pages don't close th
eir connection?
Geoff and list: I had to do some other work on Monday and Tuesday. Here's
the state of my investigations (and I appreciate knowing if others have seen
this problem):
1. Used the wkcgi adapter, and the page still hangs.
2. I haven't put prints into the WebKit code yet; I'm not familiar enough
with it to know where to start.
3. I'm running Apache 1.3.23, same as you are. I unloaded the mod_python
DSO, but still get the same results.
4. I recompiled and reinstalled mod_webkit from the head of CVS; same
results as before.
I see this behavior on two different machines on two completely different
networks.
If others see this behavior, please weigh in.
And if I could get one or two pointers to where to start putting print
statements to track down the point of hang, I'd be grateful. I'm a
procedural sort of person trying to get by in an object-oriented world :-)
Cheers!
--
David Hancock | dhancock@... | 410-266-4384
-----Original Message-----
From: Geoffrey Talvola [mailto:gtalvola@...]
Sent: Sunday, April 28, 2002 9:34 PM
To: Hancock, David (DHANCOCK); 'Geoffrey Talvola';
'webware-discuss@...'
Subject: Re: [Webware-discuss] WebKit Error traceback pages don't close th
eir connection?
On Friday April 26, 2002 02:52 pm, Hancock, David (DHANCOCK) wrote:
> I am seeing the behavior with the included Examples/Error servlet.
> One installation that demonstrates the problem can be seen at:
>
> http://dhancock.2y.net/ADC/Examples/Error
> <http://dhancock.2y.net/ADC/Examples/Error&gt;
I just visited this link - and it does wedge.
> And one more data point--while the above is a machine at home (I'm
> taking the day off!), but I see the same behavior on several Linux
> machines at work (similar configurations, just WAY faster than my home
> box).
>
> I appreciate all the attention to this issue--I hope we can find
> something and fix it.
>
> Cheers!
I can't reproduce the problem on my Linux box at home. I'm running Mandrake
8.2 with a mod_webkit built from CVS on March 24, and I'm using Webware from
the tip of CVS. And Python 2.2. The error page comes out just fine and the
connection closes -- no wedge.
At this point I would recommend:
1) Try changing to the CGI adapter and see if that helps.
2) Throw in a bunch of print statements into the WebKit code to see if you
can find a point where it's getting wedged.
3) Try updating Apache if you're using a version significantly older than
1.3.23 which is what I'm using.
4) Recompile mod_webkit from the head of CVS.
5) Find out from other people on the list whether they have the same
problem.
- Geoff

Hancock, David (DHANCOCK) wrote:
> And if I could get one or two pointers to where to start putting print
> statements to track down the point of hang, I'd be grateful. I'm a
> procedural sort of person trying to get by in an object-oriented world :-)
Try:
http://www.cyberclip.com/webdebug/
It's easy to setup, you start it running
and tell your browser to proxy through
port 2001. Then you should get all the
printed data on the webdebug admin
page to give you an idea what the
last character coming out of WebWare
is.
One caveat is that webdebug proxies
to port 80, and there might be an issue
with the redirect to the WebKit port.
--
Bill Eldridge
Radio Free Asia
bill@...

Geoff and list: I had to do some other work on Monday and Tuesday. Here's
the state of my investigations (and I appreciate knowing if others have seen
this problem):
1. Used the wkcgi adapter, and the page still hangs.
2. I haven't put prints into the WebKit code yet; I'm not familiar enough
with it to know where to start.
3. I'm running Apache 1.3.23, same as you are. I unloaded the mod_python
DSO, but still get the same results.
4. I recompiled and reinstalled mod_webkit from the head of CVS; same
results as before.
I see this behavior on two different machines on two completely different
networks.
If others see this behavior, please weigh in.
And if I could get one or two pointers to where to start putting print
statements to track down the point of hang, I'd be grateful. I'm a
procedural sort of person trying to get by in an object-oriented world :-)
Cheers!
--
David Hancock | dhancock@... | 410-266-4384
-----Original Message-----
From: Geoffrey Talvola [mailto:gtalvola@...]
Sent: Sunday, April 28, 2002 9:34 PM
To: Hancock, David (DHANCOCK); 'Geoffrey Talvola';
'webware-discuss@...'
Subject: Re: [Webware-discuss] WebKit Error traceback pages don't close th
eir connection?
On Friday April 26, 2002 02:52 pm, Hancock, David (DHANCOCK) wrote:
> I am seeing the behavior with the included Examples/Error servlet.
> One installation that demonstrates the problem can be seen at:
>
> http://dhancock.2y.net/ADC/Examples/Error
> <http://dhancock.2y.net/ADC/Examples/Error&gt;
I just visited this link - and it does wedge.
> And one more data point--while the above is a machine at home (I'm
> taking the day off!), but I see the same behavior on several Linux
> machines at work (similar configurations, just WAY faster than my home
> box).
>
> I appreciate all the attention to this issue--I hope we can find
> something and fix it.
>
> Cheers!
I can't reproduce the problem on my Linux box at home. I'm running Mandrake
8.2 with a mod_webkit built from CVS on March 24, and I'm using Webware from
the tip of CVS. And Python 2.2. The error page comes out just fine and the
connection closes -- no wedge.
At this point I would recommend:
1) Try changing to the CGI adapter and see if that helps.
2) Throw in a bunch of print statements into the WebKit code to see if you
can find a point where it's getting wedged.
3) Try updating Apache if you're using a version significantly older than
1.3.23 which is what I'm using.
4) Recompile mod_webkit from the head of CVS.
5) Find out from other people on the list whether they have the same
problem.
- Geoff

On Wed, May 01, 2002 at 02:11:29AM -0700, Chuck Esterbrook wrote:
> If I try to upload a file without actually selecting one (or typing in
> a path), the app server hangs, but just on that request.
>
> This also happens in my own application.
This happens with Netscape 4/PHP too, if you choose a directory
rather than a file.
--
-Mike (Iron) Orr, iron@... (if mail problems: mso@...)
http://iron.cx/ English * Esperanto * Russkiy * Deutsch * Espan~ol

I started playing with the python wrapper for gd from
http://www.boskant.nl/geert/Software/
and it seems to work well with Webware - as an example:
class PNG(ExamplePage):
import gd,sys,time
def writeHTML(self):
img = gd.Image(300, 200, truecolor=1)
pnt = gd.Painter(img)
pnt.setPen(gd.Pen(gd.RGBA(0, 0, 0)))
pnt.setBrush(gd.Brush(gd.RGBA(0,255,255)))
pnt.drawRectangle((0, 0), 300, 200)
font = gd.Font('mediumbold')
pnt.setFont(font)
pnt.drawText((65, 100), time.ctime(time.time()))
img.save(self,format='png')
where "img.save" nicely grabs the write method of self.
I access this from another page with:
self.writeln('<p> <img src="/WK/PNG">\n')
which works for both png & jpeg
I am curious though why I don't need to output
"Content-type: img/jpg\n\n"
from my PNG.py script which I do when outputting
from an Apache cgi.
-
Bill Eldridge
Radio Free Asia
bill@...

On Wednesday 01 May 2002 02:11 am, Chuck Esterbrook wrote:
> If I try to upload a file without actually selecting one (or typing
> in a path), the app server hangs, but just on that request.
>
> This also happens in my own application.
>
> I haven't gone hunting for this yet. I'd like to know what results
> others get first.
>
> I'm running Webware CVS, Mandrake Linux 8.1, Apache 1.3.x and
> mod_webkit or WebKit.cgi.
Happens with Mozilla 0.9.7 but NOT Opera 5.0 or Netscape 4.7 (all on
Linux).
Haven't tried with IE yet.
So maybe Mozilla sends poorly formed form data...
-Chuck

If I try to upload a file without actually selecting one (or typing in
a path), the app server hangs, but just on that request.
This also happens in my own application.
I haven't gone hunting for this yet. I'd like to know what results
others get first.
I'm running Webware CVS, Mandrake Linux 8.1, Apache 1.3.x and
mod_webkit or WebKit.cgi.
-Chuck