C.2 Threads

Tomcat uses HTTP and HTTPS threads to service incoming and outgoing requests.

HTTP threads are used for servicing content. Because the content is already encrypted, there is no need to send it securely.

HTTPS threads are used for all other communication to the Primary Server: login, refresh, and so forth.

By default, these threads are set at 200 for HTTP and 200 for HTTPS. These values can be seen in the server.xml file at:

During testing, the HTTP and HTTPS threads in the server.xml file were increased from the defaults of 200. Office 2003 was deployed to 1,000 devices and launched on refresh. This testing was done on a gigabit network. The results are as follows:

Table C-1 Results of Deploying Office 2003 to 1,000 Devices

HTTP Threads

HTTPS Threads

Results

Explanation

400

200

Failed

ZENserver dies. Java out-of-memory error.

300

300

Failed

Java out-of-memory error.

350

250

Failed

Java out-of-memory error.

350

200

Passed

Time: 35-40 minutes, Client Retries: 15 average. This is the maximum for HTTP threads.

300

200

Passed

Time: 35-40 min. Client Retries: 25 average.

200

200

Passed

Time: 35-40 min. Client Retries: 35 average.