On Sun, Jul 16, 2000 at 12:05:08PM -0500, Steve Petty wrote:
>
> We are running SSL on Apache 1.3.12 with tomcat, openssl and mod_ssl (on
> solaris boxes). We have load balanced for the optimum number of
> connections and all is working fine.
>
> However, after the user finishes, departs the last https page and leaves
> our domain, the session seems to remain active for the timeout period
> (currently set to 300 because it is needed earlier in the session). We
> have a high volume site and this is impacting the number of available new
> session connections.
>
> Is there a way to terminate an active session when the user leaves your site?
I don't know of a way, the whole point of the session cache is to speed
things up. How are the number of ssl connections you have active
affecting performance? Maybe you're confusing the ssl session cache with
the tomcat session manager? Are you using a dbm or shm ssl session cache?
I believe the dbm session cache has an unlimited size, and the shm session
cache is configurable. If you're using the shm session cache, you may
want to increase the maximum size to 1-2MB or so. Each MB of shm session
cache is good for about 6500 cached sessions (appx 150 bytes per session
I've found).
Hope this helps,
-Dave
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
