Ew, that does look rather unplesant ;-)
I've got a couple of more or less similar, but slightly older versions
running on Solaris and haven't run into a similar problem yet. But since
I'm setting up a new server in a similar setup (- mod_jserv) next week,
then I'm quite interested in helping you track this down ;-)
First, could you add some more info about your setup / configuration.
I'm thinking about the stuff you have in httpd.conf - and wether you've
got client certificates and what type of session cache you've got.
Next, do you see any pattern in the client side of things - is it always
on the initial request, is it the same client, is there some sort of
pattern to this? I know these are a bit hard to figure out, but perhaps
by collecting incidents and comparing with access logs.
Last, you could try increasing SSLLogLevel to perhaps gain more info
about just exactly what is happening.
>From the really ugly department of nasty hacks to keep your server
running until the problem has been solved, you could either set up
ulimit to limit memory available to a single process or you could set
up a daemon to kill off any httpd processes that has gone wild. Not that
this is a recommended solution, it's just a way of keeping things going.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
