OK, I made the following changes (1 at a time) to 'server.xml', and retested:
<Manager className="org.apache.catalina.ha.session.DeltaManager"
expireSessionsOnShutdown="false"
processExpiresFrequency="1"
notifyListenersOnReplication="true"/>
No discernable difference was noted on the retest (NOTE: I have measured the
sessions vs. the number of 'threads requesting pages', and I think that the
sessions are actually expiring - just _much_ slower than my load generator is
creating them. So I'm creating 100,000 sessions in 'n' time period, and in that
same time period only 6,000 are being expired and removed (the ratio seems
pretty constant - ~94% of the sessions created are staying around).
Then I made this change to 'server.xml':
<Engine
name="tomcat"
backgroundProcessorDelay="1"
defaultHost="localhost">
Again, no discernable difference in behavior.
So, new question - is there a way to tell Tomcat to clear out larger numbers of
sessions at once? (Assuming they are past their "inactivity duration" period?)
Even when I shut off the load generators, it only clears the sessions at a rate
of a few thousand every second.
--
Robin D. Wilson
Director of Web Development
KingsIsle Entertainment, Inc.
CELL: 512-426-3929
DESK: 512-623-5913
www.KingsIsle.com
-----Original Message-----
From: Robin Wilson [mailto:[email protected]]
Sent: Friday, January 08, 2010 4:10 PM
To: Tomcat Users List
Subject: RE: When running under high load (via load generating tools), Tomcat
6.0.20 stops expiring sessions until the load subsides; causing thrashing on
Garbage Collection
Thanks, I'll give that a try.
Just out of curiosity, what is the downside of doing this? (Performance hit,
???)
--
Robin D. Wilson
Director of Web Development
KingsIsle Entertainment, Inc.
CELL: 512-426-3929
DESK: 512-623-5913
www.KingsIsle.com
-----Original Message-----
From: Mark Thomas [mailto:[email protected]]
Sent: Friday, January 08, 2010 4:07 PM
To: Tomcat Users List
Subject: Re: When running under high load (via load generating tools), Tomcat
6.0.20 stops expiring sessions until the load subsides; causing thrashing on
Garbage Collection
On 08/01/2010 21:53, Robin Wilson wrote:
> Is there a setting we're missing that tells Tomcat to make session expiration
> a higher priority?
Session expirations are processed every Engine.backgroundProcessorDelay
* Manager.processExpiresFrequency seconds which by default is 10 * 6 =
60 seconds
I'd suggest reducing processExpiresFrequency first. If that is set to 1
and you still have issues then look at reducing backgroundProcessorDelay.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
