Connector configuration in Tomcat

JBoss uses Tomcat as the Web container, so the configuration of the Web container in JBoss is similar to that in Tomcat, which mainly involves editing the server.xml file. In JBoss 5.x, this file is located in ${JBOSS.HOME}\server\${confifure}\deploy\jbossweb.sar , where the value of configure can be all, default, web, standard, minimal, etc. The following code shows a server.xml file under the JBoss default configuration. Due to space reasons, the comments have been removed.

<Server> 
  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /> 
  <Listener className="org.apache.catalina.core.JasperListener" /> 
  <Service name="jboss.web"> 
   <Connector protocol="HTTP/1.1" port="8080" address="${jboss.bind.address}"  
        connectionTimeout="20000" redirectPort="8443" compression="on"  
        compressionMinSize="1" compressableMimeType="text/html,text/xml" /> 
   <Engine name="jboss.web" defaultHost="localhost"> 
     <Realm className="org.jboss.web.tomcat.security.JBossWebRealm" 
      certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping" 
      allRolesMode="authOnly" 
      /> 
     <Host name="localhost">  
      <Valve className="org.jboss.web.tomcat.service.jca.CachedConnectionValve" 
      cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager" 
      transactionManagerObjectName="jboss:service=TransactionManager" /> 
     Host> 
   Engine> 
  Service> 
Server>

In the above configuration file, Server is the root node. One Server represents a Servlet container. Therefore, there can be only one such node in server.xml. Under the Server node, there can be one or more Service nodes.

A Service node represents one or more Connectors and an Engine, and Connector and Engine are two important configuration items in server.xml. The main function of Connector is to accept and respond to user requests. Commonly used Connectors include HTTP/1.1 Connector and AJP Connector. HTTP/1.1 Connector is mainly used to process user HTTP requests. It should be noted that although it is called HTTP/1.1 Connector, it is fully compatible with HTTP/1.0 protocol. AJP Connector mainly uses the AJP protocol to communicate with Web Connector and is usually used in a cluster.

The HTTP/1.1 Connector instance listens on the port configured by the user. When the application server starts, the HTTP/1.1 Connector is responsible for creating several threads to process user requests. The number of threads created depends on the minThreads value configured by the user, which defaults to 5. When more user requests arrive, the HTTP/1.1 Connector will create more threads to process requests. The maximum number of threads created is defined by maxThreads, and the default value is 20. When all threads are busy processing user requests, new incoming requests will be placed in the Socket queue created by the HTTP/1.1 Connector. The length of the queue is defined by the acceptCount attribute. When the waiting queue is also full, new user requests will receive a connection refused error.

All the configuration items provided by Connector (incomplete scheme, isSecure, xpoweredBy, useIPVHosts):

• allowTrace If the server needs to be able to handle user HAED/TRACE requests, this value should be set to true. The default value is false;
• emptySessionPath If set to true, the path of all session and cookie will be set to /. This setting is usually useful in portlets. The default value is false;
• enableLookups If you need to get the client's machine name when calling the request.getRemoteHost() method, you need to configure it to true. If it is configured to false, the DNS query will be skipped and the IP address of the client machine will be directly returned. Usually, in order to improve performance, this value is set to false. The default value is true;
• maxPostSize The maximum size of data that can be submitted by the POST method. If not declared or set to less than or equal to 0, it means that the size of data submitted by POST is unlimited. The default value is 2Megabytes.
• protocol sets the protocol for processing requests. The default is HTTP/1.1, i.e. org.apache.coyote.http11.Http11Protocol. Other supported protocols include: org.apache.coyote.http11.Http11NioProtocol (processing user requests through NIO can improve system performance) and org.apache.coyote.http11.HttpAprProtocol.
• proxyName/proxyPort If the Web server uses a proxy server, configuring this parameter means that when calling request.getServerName, the name of the proxy server will be obtained, and getServerPort() will return proxyPort.
• redirectPort If the Connector is configured to support non-SSL requests, when an SSL request comes in, the server will automatically redirect the request to redirectPort.
• URIEncoding The encoding method when URI bytes are converted into String. The default is ISO-8859-1. If the page needs to support Chinese, it can generally be set to UTF-8 or GBK, GB2312.
• useBodyEncodingForURI If set to true, the URI encoding method will be determined based on the page encoding. The default is false.

Configuration items provided by Http/1.1 Connector:

• acceptCount The length of the waiting queue. The default value is 100.
• address If the host where Tomcat is located has multiple IPs, this value declares the IP address used to listen for HTTP requests.
• bufferSize The size of the input stream created by the Connector. The default value is 2048 bytes. Increasing this value can improve performance and increase memory consumption.
• compressableMimeType uses HTTP compressed MIME types, separated by commas. The default values ​​are text/html, text/xml, text/plain.
• compression To save bandwidth, you can set this value to on to enable HTTP/1.1 GZIP compression. off turns off compression, forces force compression, the default value is off.
• connectionTimeout The time (milliseconds) that the Connector waits after accepting a connection. The default value is 60000.
• executor Under the Service node, an Executor node can be configured before the Connector node to manage threads. The value of this property is the name of the configured Executor. If this property is applied and the executor exists, any other configuration about threads will be ignored.
• keepAliveTimeout The number of microseconds that the Connector waits for another Keep Alive request before closing the connection. The default value is the same as connectionTimeout.
• maxHttpHeaderSize The maximum size of HTTP request and response header information. The default value is 8192 bytes.
• maxKeepAliveRequests The maximum number of requests for HTTP/1.0 Keep Alive and HTTP/1.1 Keep Alive / Pipeline. If set to 1, Keep Alive and Pipeline will be disabled. If set to a number less than 0, there will be no limit on the maximum number of Keep Alive requests. The default is 100.
• maxThreads The maximum number of threads used to process user requests. The default value is 20.
• noCompressionUserAgents: Sets the clients that do not use HTTP GZIP compression, separated by commas. This attribute can be used when some browsers do not support compression.
• port The port that the Connector listens on.
• restrictedUserAgents sets the client agent names that do not use Keep Alive, separated by commas. The default value is an empty string.
• server overrides the serve header of the HTTP response. If not set, the default value is Apache-Coyote/1.1. Normally, you don't need to pay attention to this property.
• socketBuffer The size of the Socket output stream buffer. The default is 9000 bytes. If it is set to a value less than 0, it means that this buffer is not used.
• The default value of tcpNoDelay is true. Setting it to true can improve system performance.
• threadPriority The priority of the request processing thread. The default priority is NORMAL.

Summarize

The above is the full content of this article. I hope that the content of this article will have certain reference learning value for your study or work. Thank you for your support of 123WORDPRESS.COM. If you want to learn more about this, please check out the following links