Re: Apache-print Timed Out

2002-07-22 Thread David Wheeler

On 7/21/02 8:19 AM, Ask Bjoern Hansen [EMAIL PROTECTED] claimed:

 You didn't tell which version of MSIE they use; but if it's not
 recent it could be some CSS that makes the browser act up[1].

V.5, I think. It doesn't happen on OS X, though, only OS 9.

David

-- 
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/  Yahoo!: dew7e
   Jabber: [EMAIL PROTECTED]





Re: Apache-print Timed Out

2002-07-18 Thread Chris Newman

This may be a long shot but the circumstances sound familiar. I had a problem
where an HTTP connection was simply not being properly closed and Netscape4
was just hanging around waiting for the response to finish whereas other
browsers/platforms had no problem, ie. the other browsers were
auto-cancelling the delayed response. Connecting to port 80 over telnet also
clearly showed the connection was simply not closing and I modified the java
proxy server source in an attempt to hammer blow the connection. Turns out
that the JRE needed upgrading on the proxy and the I/O worked properly.
My point is it may well be nothing at all to do with Apache/mod_perl. I had
been trying to debug the PHP engine on the server but telnetting from the
proxy to the server showed the connection was closing correctly so it had to
be the proxy's fault.

as I said, this may be a long shot.

chris

On Thursday 18 Jul 2002 3:21 pm, you wrote:
 On 7/10/02 10:37 AM, David Wheeler [EMAIL PROTECTED] claimed:
  I have a couple of strange bugs showing up in Bricolage that have
  something to do with Apache-print timing out (with Win 95 and Mac OS 9
  -- yes, these folks need to join the new millennium), and have no idea
  how or under what circumstances print times out.

 Okay, I've got the output of some tcpdump runs in Bricolage Bugzilla.


 http://bricolage-bugzilla.thepirtgroup.com/showattachment.cgi?attach_id=35

 All they demonstrate, however, is that Apache/mod_perl never finishes
 sending the page to the browser. One page is 32120 bytes, and the other is
 36500 bytes. I really have no clue what could be causing this. Why should
 Apache-print ever time out?  I didn't even know that timing out was
 something that a print method could do. And why does it only happen for
 some browser/platform combinations?

 Anyone who has some ideas, or who can suggest other approaches to
 diagnosing the problem, will get a great deal of gratitude from me and many
 Bricolage users.

 Thanks,

 David

---



Re: Apache-print Timed Out

2002-07-18 Thread Perrin Harkins

David Wheeler wrote:
  Why should Apache-print ever time out?

One reason could be a web client that disconnects.  There could also be 
a dropped network connection or one that's too slow.  I think you can 
adjust this behavior with the TimeOut directive in httpd.conf.

 I didn't even know that timing out was
 something that a print method could do.

This isn't the same thing as CORE::print.  It's overriden for mod_perl 
to send to the network.  Even CORE::print can return false in certain 
conditions, like when writing a file when the disk is full.

 And why does it only happen for some
 browser/platform combinations?

Probably buggy browsers or TCP stacks.

- Perrin




Re: Apache-print Timed Out

2002-07-10 Thread David Wheeler

I think I made a mistake posting this query over the holiday weekend, so I'm
gonna speak up again.

I have a couple of strange bugs showing up in Bricolage that have something
to do with Apache-print timing out (with Win 95 and Mac OS 9 -- yes, these
folks need to join the new millennium), and have no idea how or under what
circumstances print times out.

Any enlightenment on this issue would be most welcome.

Thanks!

David

On 7/5/02 1:25 PM, David Wheeler [EMAIL PROTECTED] claimed:

 Hi All,
 
 I'm seeing some strange behavior with IE/Mac OS Classic where pages aren't
 getting completely loaded and I'm seeing this message in the log error log:
 
 [Fri Jul  5 20:22:17 2002] [info] [client 192.168.1.1] mod_perl:
 Apache-print timed out
 
 Config:
 
 Apache/1.3.26 (Unix) mod_perl/1.27 mod_ssl/2.8.9 OpenSSL/0.9.6b
 
 This is on RedHat Linux 7.2.
 
 I did a quick google search, but found no obvious answers to this issue.
 Anyone got any ideas what could be happening? Why and under what
 circumstances will Apache-print time out?
 
 TIA,
 
 David

-- 
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/  Yahoo!: dew7e
   Jabber: [EMAIL PROTECTED]





Apache-print Timed Out

2002-07-05 Thread David Wheeler

Hi All,

I'm seeing some strange behavior with IE/Mac OS Classic where pages aren't
getting completely loaded and I'm seeing this message in the log error log:

[Fri Jul  5 20:22:17 2002] [info] [client 192.168.1.1] mod_perl:
Apache-print timed out

Config:

Apache/1.3.26 (Unix) mod_perl/1.27 mod_ssl/2.8.9 OpenSSL/0.9.6b

This is on RedHat Linux 7.2.

I did a quick google search, but found no obvious answers to this issue.
Anyone got any ideas what could be happening? Why and under what
circumstances will Apache-print time out?

TIA,

David

-- 
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/  Yahoo!: dew7e
   Jabber: [EMAIL PROTECTED]