Hello,
I am currently working on a web application deployed on a old GlassFish 2.1
Patch 2.
i have changed the keep alive timeout to 120 sec from 30 sec but nothing
change at all unless i configure the acceptor thread of my http listener to
1.
I found that it was a bug fixed in GlassFish 2.1.1 Patch 8 : 6831879
Keepalive timeout is ignored if acceptor thread configured greater than 1.
I have installed GlassFish 2.1.1 Patch 9 but the bug seems not to be fixed.
When my listener acceptor thread is configured to 1 it is OK, connexions
are closed after 120 sec of inactivity but when i configure my listener
acceptor thread with more than 1 thread, connexions are closed after 30 sec.
Am i missing something ?
my domain.xml conf :
<http-service>
<http-listener acceptor-threads="4" address="0.0.0.0"
blocking-enabled="false" default-virtual-server="server" enabled="true"
family="inet" id="http-listener-1" port="8080" security-enabled="false"
server-name="" xpowered-by="true">
<property name="compression" value="force"/>
</http-listener>
<http-listener acceptor-threads="1" address="0.0.0.0"
blocking-enabled="false" default-virtual-server="__asadmin" enabled="true"
family="inet" id="admin-listener" port="4848" security-enabled="false"
server-name="" xpowered-by="true"/>
<virtual-server hosts="${com.sun.aas.hostName}"
http-listeners="http-listener-1" id="server"
log-file="${com.sun.aas.instanceRoot}/logs/server.log" state="on">
<property name="docroot"
value="${com.sun.aas.instanceRoot}/docroot"/>
<property name="accesslog"
value="${com.sun.aas.instanceRoot}/logs/access"/>
<property name="sso-enabled" value="false"/>
</virtual-server>
<virtual-server hosts="${com.sun.aas.hostName}"
http-listeners="admin-listener" id="__asadmin"
log-file="${com.sun.aas.instanceRoot}/logs/server.log" state="on">
<property name="docroot"
value="${com.sun.aas.instanceRoot}/docroot"/>
<property name="accesslog"
value="${com.sun.aas.instanceRoot}/logs/access"/>
<property name="sso-enabled" value="false"/>
</virtual-server>
<request-processing header-buffer-length-in-bytes="8192"
initial-thread-count="64" request-timeout-in-seconds="30" thread-count="128"
thread-increment="4"/>
<keep-alive max-connections="10000" thread-count="4"
timeout-in-seconds="120"/>
<connection-pool max-pending-count="4096" queue-size-in-bytes="4096"
receive-buffer-size-in-bytes="4096" send-buffer-size-in-bytes="8192"/>
<http-protocol default-response-type="AttributeDeprecated"
default-type="text/html; charset=iso-8859-1" dns-lookup-enabled="false"
forced-response-type="AttributeDeprecated" forced-type="text/html;
charset=iso-8859-1" ssl-enabled="true" version="HTTP/1.1"/>
<http-file-cache file-caching-enabled="false"
file-transmission-enabled="false" globally-enabled="false"
hash-init-size="0" max-age-in-seconds="30" max-files-count="1024"
medium-file-size-limit-in-bytes="537600"
medium-file-space-in-bytes="10485760" small-file-size-limit-in-bytes="2048"
small-file-space-in-bytes="1048576"/>
<property name="accessLoggingEnabled" value="true"/>
<property name="accessLogWriteInterval" value="1"/>
<property name="accessLogBufferSize" value="65536"/>
</http-service>
Thanks
--
View this message in context: http://old.nabble.com/glassfish-2.1.1-Keepalive-timeout-is-ignored-if-acceptor-thread-configured-greater-than-1-tp30748058p30748058.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.