orted the connection.
>
Ok, I will look some more at this. It could be related to the problems
we're having. Still I think it's weird that ab quits over this.
Thank you for your time Stas :-)
mvh.
Anders Nielsen
On Fri, 2005-03-18 at 17:37 -0500, Stas Bekman wrote:
> Anders, the first priority is to figure out how to reproduce the problem
> at will. If you don't manage that, you most likely are going to waste
> hours staring at the screen. I'd concentrate on that task first.
>
> Try using ab (apachebenc
On Fri, 2005-03-18 at 11:15 -0500, Stas Bekman wrote:
> Anders, do you by chance use a proxy that may have eaten the response?
>
> What do you see in logs/access_log, it tells how many bytes were sent to
> the client.
>
> What happens if you replace print($x) with Apache->request->print($x)
>
On Wed, 2005-03-16 at 21:11 -0500, Stas Bekman wrote:
> Please see:
> 21.7. Hanging Processes: Detection and Diagnostics
> http://modperlbook.org/html/ch21_07.html
>
Thank you for the reply.
The problem I described happened again and I was able to get some more
information.
The server isn't act
I would like to add that no messages are seen in the error logs. We are
using Apache/1.3.29 and mod_perl/1.29 on Redhat linux.
mvh
Anders Nielsen
o handle these
parts.
The problem occurred again on all 3 servers at the same time. This has
led me to believe that the problem might be related to the operating
system. Perhaps some resource that is being overused. I am out of ideas
however.
Hope this list can help.
Thanks in advance.
Anders Nielsen
