You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by jf...@apache.org on 2002/11/05 12:41:49 UTC
cvs commit: jakarta-tomcat-4.0/catalina/src/conf server.xml
jfclere 2002/11/05 03:41:49
Modified: catalina/src/conf server.xml
Log:
Arrange the explainations about maxActiveSessions and minIdleSwap.
Revision Changes Path
1.64 +7 -6 jakarta-tomcat-4.0/catalina/src/conf/server.xml
Index: server.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/conf/server.xml,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -r1.63 -r1.64
--- server.xml 22 Oct 2002 09:45:34 -0000 1.63
+++ server.xml 5 Nov 2002 11:41:49 -0000 1.64
@@ -307,14 +307,15 @@
ignored in both cases.
maxActiveSessions: If 0 or greater, having too many active
sessions will result in some being swapped out. minIdleSwap
- limits this. -1 means unlimited sessions are allowed.
- 0 means sessions will almost always be swapped out after
- use - this will be noticeably slow for your users.
+ limits this. -1 or 0 means unlimited sessions are allowed.
+ If it is not possible to swap sessions new sessions will
+ be rejected.
+ This avoids thrashing when the site is highly active.
minIdleSwap: Sessions must be idle for at least this long
(in seconds) before they will be swapped out due to
- maxActiveSessions. This avoids thrashing when the site is
- highly active. -1 or 0 means there is no minimum - sessions
- can be swapped out at any time.
+ activity.
+ 0 means sessions will almost always be swapped out after
+ use - this will be noticeably slow for your users.
maxIdleSwap: Sessions will be swapped out if idle for this
long (in seconds). If minIdleSwap is higher, then it will
override this. This isn't exact: it is checked periodically.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>