Endre Stølsvik wrote:
> My config is like this:
>
> <Connector className="org.apache.catalina.connector.http.HttpConnector"
> port="##HTTPPORT##" minProcessors="1" maxProcessors="3"
> acceptCount="100" debug="99" connectionTimeout="60000"/>
>
> This gives me lots of left out small gifs, maybe a leftout stylesheet, or
> the whole document.. or whatever.
>
> I realize that there's not many processors configured here, but why does
> it start to reject connections? It should stack them in a queue, shouldn't
> it? What am I doing wrong?
>
The basic function of the HttpConnector class is to perform the
following loop over and over again:
* Wait for an incoming socket connection
* Assign it to an available processor
When you define maxProcessors as 3, you are saying that you want Tomcat
to handle up to three simultaneous connections to
remote clients. In an HTTP/1.0 environment, that many processors would
be able to handle a large number of clients if the
request rate was low, because each request is an individual socket
connection.
However, in an HTTP/1.1 environment (if your client supports it), Tomcat
supports persistent connections. In such a case,
the first three clients will grab all the available processors, and
maintain those connections for later use. For clients
that perform large numbers of requests, this is a huge win -- for
clients that are grabbing occasional images, it is rather
wasteful. You might consider using the HTTP/1.0 connector for this type
of use. Simply change the class name to
org.apache.catalina.connector.http10.HttpConnector
>
> 2001-02-25 12:49:21 HttpProcessor[10080][2] An incoming request is being assigned
> 2001-02-25 12:49:21 HttpProcessor[10080][2] The incoming request has been awaited
> 2001-02-25 12:49:21 HttpConnector[10080] No processor available, rejecting this
>connection
> 2001-02-25 12:49:21 HttpProcessor[10080][2] parseConnection:
>address=endresin.intra.coretrek.com/10.0.0.14, port=10080
>
> Does the HttpConnector have any relation to the three other lines here,
> HttpProcessor? Could anyone just give me the briefest explanation of
> what's going on in theese four lines?
>
They are related (because they are all associated with the connector you
have listening on port 10080). a request was handed
off to processor #2 -- but while it was being processed, another request
also came in. Because there were no more available
processors, that one was refused -- but the handling of the previously
allocated request (to processor #2) continues anyway.
>
> Thanks a lot! Looking forward to both the 3.3 and 4.0! Especially the
> promised proper reloading of webapps in 4!
>
In 4.0, just put your classes in WEB-INF/classes and automatic reloading
will recognize changes to them. You can also use
the management app to request a reload of *any* webapp -- whether or not
it has been configured for auto reload.
>
> --
> Mvh,
> Endre
>
Craig McClanahan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
