| Oliver 2004-01-19, 8:21 am |
| Hi,
take a look to the native.log on the HTTP-Server where the websphere
plugin ist installed.
You can configure the HTTP-Transport between the plungin and the
App.-Server as follow:
Under Services, where you define the communication port for example
Port 9080 there are 4 Parameters:
ConnectionIOTimeOut or I/O Timeout
The maximum time (in seconds) to wait when trying to read or write
data DURING a request.
The value of this property, after it is specified for the first
transport, will be applied globally to all other HTTP transports in
this administrative domain.
ConnectionKeepAliveTimeOut or Keep Alive Timeout
The maximum time (in seconds) to wait for the next request on a keep
alive connections.
The value of this property, after it is specified for the first
transport, will be applied globally to all other HTTP transports in
this administrative domain.
Maximum Keep Alives or MaxKeepAliveConnections
The maximum number of concurrent keep alive (persistent) connections
across all HTTP transports. (HTTP 1.1 allows multiple requests to be
sent on the same TCP/IP connection.) The default value is 90% of the
maximum number of threads in the Web container thread pool. This
prevents all of the threads from being held by keep alive connections
so that there are threads available to handle new incoming connect
requests.
The value of this property, after it is specified for the first
transport, will be applied globally to all other HTTP transports in
this administrative domain.
Maximum Requests per Keep Alive or MaxKeepAliveRequests
The maximum number of requests which can be processed on a single keep
alive connection.
The value of this property, after it is specified for the first
transport, will be applied globally to all other HTTP transports in
this administrative domain.
disable the ConnectionKeepAliveTimeOut (0 seconds - default is 5 s)and
take a look to the native.log
good luck
olli
"jfarney" <jf@some.email.com> wrote in message news:<bnp3k5$9mlc$1@news.boulder.ibm.com>...quote:
> We are running IBMHttpServer in a DMZ - which uses WebSphere plugin to
> interact
> with a WebSphere Cluster.
>
> We are getting Http 408 Erros with this message returned to the Browser:
> "408 Connection timed out while reading request"
>
> This problem is very difficult to reproduce as it happens randomly.
> Can anyone shed any light on this - what
|