From: fhanik Date: Tue, 27 Feb 2007 16:43:33 +0000 (+0000) Subject: Add and correct documentation X-Git-Url: https://git.internetallee.de/?a=commitdiff_plain;h=f34b9bd5415aa42a5f44caabfada19632b5c875c;p=tomcat7.0 Add and correct documentation git-svn-id: https://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk@512313 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/java/org/apache/tomcat/util/net/SocketProperties.java b/java/org/apache/tomcat/util/net/SocketProperties.java index f7569d217..d60e3d3df 100644 --- a/java/org/apache/tomcat/util/net/SocketProperties.java +++ b/java/org/apache/tomcat/util/net/SocketProperties.java @@ -42,7 +42,7 @@ public class SocketProperties { * 0 is disabled * >0 the max number of objects to keep in cache. */ - protected int eventCache = -1; + protected int eventCache = 500; /** diff --git a/webapps/docs/config/http.xml b/webapps/docs/config/http.xml index 901558834..fe7024dd8 100644 --- a/webapps/docs/config/http.xml +++ b/webapps/docs/config/http.xml @@ -412,10 +412,10 @@

Whether to allow comet servlets or not, Default value is true.

- - -

Boolean value, whether to use direct ByteBuffers or java mapped ByteBuffers. Default is true

+

Boolean value, whether to use direct ByteBuffers or java mapped ByteBuffers. Default is true +
When you are using direct buffers, make sure you allocate the appropriate amount of memory for the + direct memory space. On Sun's JDK that would be something like -XX:MaxDirectMemorySize=256m

The socket receive buffer (SO_RCVBUF) size in bytes. Default value is 25188

@@ -426,12 +426,14 @@

Each connection that is opened up in Tomcat get associated with a read and a write ByteBuffer This attribute controls the size of these buffers. By default this read buffer is sized to match the - socket read buffer (SO_RCVBUF) value, but can be sized separately.

+ socket read buffer (SO_RCVBUF) value, but can be sized separately. + For an extreme amount of keep alive connections, decrease this number of increase your heap size.

Each connection that is opened up in Tomcat get associated with a read and a write ByteBuffer This attribute controls the size of these buffers. By default this write buffer is sized to match the - socket read buffer (SO_SNDBUF) value, but can be sized separately.

+ socket read buffer (SO_SNDBUF) value, but can be sized separately. + For an extreme amount of keep alive connections, decrease this number of increase your heap size.

The Nio connector uses a class called NioChannel that holds elements linked to a socket. @@ -494,22 +496,23 @@

The third value for the performance settings. Default is 1, see Socket Performance Options

- - The max selectors to be used in the pool, to reduce selector contention. + +

The max selectors to be used in the pool, to reduce selector contention. Use this option when the command line o.a.t.u.net.NioSelectorShared value is set to false. - Default value is 200. + Default value is 200.

- - The max spare selectors to be used in the pool, to reduce selector contention. + +

The max spare selectors to be used in the pool, to reduce selector contention. When a selector is returned to the pool, the system can decide to keep it or let it be GC:ed. Use this option when the command line o.a.t.u.net.NioSelectorShared value is set to false. - Default value is -1 (unlimited) + Default value is -1 (unlimited)

- - The following command line options are available for the NIO connector:
+ +

The following command line options are available for the NIO connector:
-Dorg.apache.tomcat.util.net.NioSelectorShared=true|false - default is true. Set this value to false if you wish to use a selector for each thread. the property. If you do set it to false, you can control the size of the pool of selectors by using the + selectorPool.maxSelectors attribute