empty documents

[Fr�d�ric Schwien <fr...@igtech.fr>]

hi,

I'm using modperl 1.21 and apache 1.3.6, on Redhat 6.0.
I'm also using Text:::Template and Apache::Dbi for persistent connections on a
Mysql database.
 It happens sometimes , on some scripts, that I get an empty document. I do not
thing it's something to deal with the "Morning Bug" that the Modperl
documentation is talking about.
It's very randomly. This error occurs 1 time over 10 on some scripts , it
happens at each request on some other.
And I do not find any link between them that could get this message.
I check for each new sensible variable if it is defined or not, I do not get
any 500 error or message in the error log . 
I'm wondering if it comes from my cgi scripts, from my Apache configuration,
from Apache::Dbi on Mysql , or anything else???? 

Does anybody had the same problem ?
I'm on a test server with just 64 MB of RAM, then only accepting Max 7 Clients.

Thanks,

Fred

--
*****************************************
Here is a sample of my httpd.conf :
*****************************************
Timeout 300
 
#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On
#KeepAlive Off
 
#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100
#MaxKeepAliveRequests 10
 
#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
#KeepAliveTimeout 15
KeepAliveTimeout 15
 
#
# Server-pool size regulation.  Rather than making you guess how many
# server processes you need, Apache dynamically adapts to the load it
# sees --- that is, it tries to maintain enough server processes to
# handle the current load, plus a few spare servers to handle transient
# load spikes (e.g., multiple simultaneous requests from a single
# Netscape browser).
#
# It does this by periodically checking how many servers are waiting
# for a request.  If there are fewer than MinSpareServers, it creates
# a new spare.  If there are more than MaxSpareServers, some of the
# spares die off.  The default values are probably OK for most sites.
#
MinSpareServers 5
MaxSpareServers 10
#MinSpareServers 2
#MaxSpareServers 2
 
#
# Number of servers to start initially --- should be a reasonable ballpark
# figure.
#
StartServers 2
 
#
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
#
#MaxClients 150
MaxClients 7