User: mulder
Date: 00/10/08 08:05:07
Modified: manual adv_config.html
Log:
Update Minerva parameters and defaults.
Revision Changes Path
1.8 +37 -21 jbossweb/manual/adv_config.html
Index: adv_config.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/adv_config.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- adv_config.html 2000/10/03 12:06:21 1.7
+++ adv_config.html 2000/10/08 15:05:07 1.8
@@ -222,7 +222,7 @@
that requests a connection will wait until one is available.
If set to <strong>false</strong>, then the pool will return
null immediately (and the client may retry).</td>
- <td>false</td>
+ <td>true</td>
</tr>
<tr>
<td>LoggingEnabled</td>
@@ -239,7 +239,11 @@
This would catch things like a client that disconnects
suddenly without closing database connections gracefully,
or queries that take an unexpectedly long time to run. This
- is not generally useful in an EJB environment.</td>
+ is not generally useful in an EJB environment, though it may
+ be for stateful session beans that keep a DB connection as
+ part of their state. This is in contrast to the idle
+ timeout, which closes connection that have been idle in the
+ pool.</td>
<td>false</td>
</tr>
<tr>
@@ -256,30 +260,42 @@
<td>120000 (2m)</td>
</tr>
<tr>
- <td>ShrinkingEnabled</td>
+ <td>IdleTimeoutEnabled</td>
<td>Whether the pool should close idle connections. This
prevents the pool from keeping a large number of connections
- open indefinitely after a spike in activity. There is no
- guarantee about when a particular connection will be closed,
- only that the pool size will be reduced and only connections
- idle for a long time will be removed.</td>
+ open indefinitely after a spike in activity. Any connection
+ that has been unused in the pool for longer than this amount
+ of time will be closed. If you do not want the pool to
+ shrink so rapidly, you can set the MaxIdleTimeoutPercent
+ and then some connections will be recreated to replace the
+ closed ones. This is in contrast to garbage collection,
+ which returns connections to the pool that have been checked
+ out of the pool but not returned for a long period of
+ time.</td>
<td>false</td>
</tr>
- <tr>
- <td>ShrinkPercent</td>
- <td>Sets the percent of idle connections to close, as a fraction
- between 0 and 1 (though there is a minimum of 1 connection if
- are eligible). If set to 1, all connections idle for more
- than the specified time will be closed. If set to 0, only 1
- connection will be released each time (if there's one that's
- been idle long enough).</td>
- <td>0.33</td>
- </tr>
<tr>
- <td>ShrinkMinIdleTime</td>
- <td>Set the minimum idle time (in milliseconds) before a
- connection is eligible for shrinking.</td>
- <td>600000 (10m)</td>
+ <td>MaxIdleTimeoutPercent</td>
+ <td>Sets the idle timeout percent as a fraction between 0 and 1.
+ If a number of connections are determined to be idle, they
+ will all be closed and removed from the pool. However, if the
+ ratio of objects released to objects in the pool is greater
+ than this fraction, some new objects will be created to
+ replace the closed objects. This prevents the pool size from
+ decreasing too rapidly. Set to 0 to decrease the pool size by
+ a maximum of 1 object per test, or 1 to never replace objects
+ that have exceeded the idle timeout. The pool will always
+ replace enough closed connections to stay at the minimum
+ size.</td>
+ <td>1.0</td>
+ </tr>
+ <tr>
+ <td>IdleTimeout</td>
+ <td>Set the idle timeout for unused connections. If a
+ connection has been unused in the pool for this amount of
+ time, it will be released the next time garbage collection
+ and shrinking are run (see GCInterval).</td>
+ <td>1800000 (30m)</td>
</tr>
<tr>
<td>TimestampUsed</td>
