The standard implementation of JK/AJP Connector is org.apache.ajp.tomcat4.Ajp13Connector.
This implementation supports the JK 1.3 and 1.4 protocols (also known as AJP 1.3 and 1.4).
It supports the following additional attributes (in addition to the common attributes listed above):
acceptCount
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.
address
For servers with more than one IP address, this attribute specifies which address will be used for listening on the specified port. By default, this port will be used on all IP addresses associated with the server.
debug
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).
maxProcessors
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.
NOTE:For Apache 1.3 on Unix there is a 1 to 1 mapping between httpd processes and Ajp13Processors. You must configure maxProcessors to be greater than or equal to the maximum number of httpd processes your Apache web server spawns.
minProcessors
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.
port
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.
tomcatAuthentication
This flag, which value defaults to true
, indicates whether or not authentication will be handled by Tomcat or the native web server. If the attribute value is true
, any pricipal authenticated by the native web server will be ignored, and Tomcat will take care of the authentication. If the attribute value is false
, Tomcat will not attempt to authenticate a principal if the native web server has already authenticated one.