Skip to content

Overview

Concepts and Principles

Development

Overview

IDEs

API Explorer

Releases

Release Notes

TORO Integrate

Coder Studio

Coder Cloud

Bug Reports

Search

Tomcat

TORO Integrate ships with Apache Tomcat, and uses it for serving all HTTP requests. Since it's included in TORO Integrate, configuring it is slightly different than usual, but it's still easy.

HTTP and HTTPS ports

If you would like to configure the HTTP and HTTPS ports, please click here

Any properties related to the HTTP Connector in Tomcat that aren't already documented here are simply added to the TORO Integrate Application Properties, using either an http or https prefix, depending on which connector you would like to configure.

For example, if you would like to enable TRACE requests to TORO Integrate, add a property called http.allowTrace and set it to true.

Properties which may be of interest when tuning TORO Integrate's Tomcat server include (in alphabetical order):

Property Name Description
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 100.
acceptorThreadCount The number of threads to be used to accept connections. Increase this value on a multi CPU machine, although you would never really need more than 2. Also, with a lot of non keep alive connections, you might want to increase this value as well. Default value is 1.
maxConnections The maximum number of connections that the server will accept and process at any given time. When this number has been reached, the server will accept, but not process, one further connection. This additional connection be blocked until the number of connections being processed falls below maxConnections at which point the server will start accepting and processing new connections again.
maxThreads 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 200. If an executor is associated with this connector, this attribute is ignored as the connector will execute tasks using the executor rather than an internal thread pool. Note that if an executor is configured any value set for this attribute will be recorded correctly but it will be reported (e.g. via JMX) as -1 to make clear that it is not used.
minSpareThreads The minimum number of threads always kept running. This includes both active and idle threads. If not specified, the default of 10 is used.
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. If the special value of 0 (zero) is used, then Tomcat will select a free port at random to use for this connector. This is typically only useful in embedded and testing applications.

Another example could be as follows:

  • HTTP running on port 80
  • HTTP not allowed more than 10 threads
  • HTTPS running on port 443
  • HTTPS using a keystore file located at /home/toro-integrate/keystore, with password 12345ABCDE
  • HTTPS has 5 threads that accept connections

The properties changed and added to TORO Integrate would be as follows:

1
2
3
4
5
6
7
http.port=80
http.maxThreads=10

https.port=443
https.keystoreFile=/home/toro-integrate/keystore
https.keystorePass=12345ABCDE
https.acceptorThreadCount=5