Top Level Elements
IMPORTANT NOTE: The Webapp connector is now deprecated. Use the
Coyote JK Connector with
The Webapp Connector element represents a
Connector component that communicates with a web
connector via the
WARP protocol. This is used for cases
where you wish to invisibly integrate Tomcat 4 into an existing (or new)
Apache installation, and you want Apache to handle the static content
contained in the web application, and/or utilize Apache's SSL
processing. In many application environments, this will result in
better overall performance than running your applications under
Tomcat stand-alone using the
HTTP/1.1 Connector. However, the only way
to know for sure whether it will provide better performance for
your application is to try it both ways.
FIXME - general description of what happens at server
startup time when you have the WARP Connector configured.
All implementations of Connector
support the following attributes:
Java class name of the implementation to use. This class must
You must specify the standard value defined below.
true if you want calls to
request.getRemoteHost() to perform DNS lookups in
order to return the actual host name of the remote client. Set
false to skip the DNS lookup and return the IP
address in String form instead (thereby improving performance).
By default, DNS lookups are disabled.
If this Connector is supporting non-SSL
requests, and a request is received for which a matching
<security-constraint> requires SSL transport,
Catalina will automatically redirect the request to the port
number specified here.
Set this attribute to the name of the protocol you wish to have
returned by calls to
example, you would set this attribute to "
for an SSL Connector. The default value is "
Set this attribute to
true if you wish to have
request.isSecure() to return
for requests received by this Connector (you would want this on an
SSL Connector). The default value is
FIXME - Update the above descriptions for anything
that the WARP Connector delegates to Apache.
The standard implementation of Webapp Connector is
It supports the following additional attributes (in addition to the
common attributes listed above):
The maximum queue length for incoming connection requests when
all possible request processing threads are in use. Any requests
received when the queue is full will be refused. The default
value is 10.
The debugging detail level of log messages generated by this
component, with higher numbers creating more detailed output.
If not specified, this attribute is set to zero (0).
The maximum number of request processing threads to be created
by this Connector, which therefore determines the
maximum number of simultaneous requests that can be handled. If
not specified, this attribute is set to 20.
The number of request processing threads that will be created
when this Connector is first started. This
attribute should be set to a value smaller than that set for
maxProcessors. The default value is 5.
The TCP port number on which this Connector
will create a server socket and await incoming connections. Your
operating system will allow only one server application to listen
to a particular port number on a particular IP address.
Set the applications base directory for Hosts
created via WARP.
The default value is "webapps".
mod-webapp offers a specific Engine when running the
Webapp Connector in its own
This Engine allows webapp to create and to map the
Hosts corresponding to the VirtualHost defined in the
The standard implementation of Webapp Engine is
It supports the standard Engine.
FIXME - Document any special features supported by the