Help!

[Mike Cantone]

I have one remaining, but somewhat glaring problem. After I use my ASP 
application for a little while (not really that long actually - maybe a 
dozen transactions), the exact same user behavior seems to cause  the 
transaction to hang. The response times seem to get a bit worse and a 
bit worse until finally it changes doesn't come back. I usually end up 
 restarting the web server at this point (hard to do in production!) 
and it doesn't seem to die easily. I issue a couple of stops - sometimes 
as many as 3-4 until it reports actually being stopped. Then I clear out 
the session cache, restart and it seems fine. If I don't clear out the 
session cache, I think it predictably is still in a funky state - 
certainly much of the time it is.

I thought maybe the Reload directive I was using for development (to 
force the Perl Modules to get reloaded when they have been changed) 
might be using up a lot of memory, but commenting this out doesn't 
really seem to help things.

The application I'm testing doesn't store a lot in session though I've 
specified MLDBM for StateDB. If the session data *were* growing too 
large, is there any warning? Do I just lose session data or do I 
crash/hang? As I said though, I am using the recommended MLDBM.

P.S. This is considerably lower priority (unless it is related to the 
above somehow), but is there any difference between using IncludesDir 
directive and PerlSwitches -I directives? Advantages/disadvantages?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]