Threads; Section C.2, "Threads - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - SYSTEM PLANNING-DEPLOYMENT-BEST PRACTICES GUIDE 10.3 30-03-2010 System Planning Manual

Java memory allocations for both zenserver and zenloader can be found by using the following
utilities:
Windows: Run
Linux: Edit
zenloader
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
Windows:
Linux:
During testing, the HTTP and HTTPS threads in 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:
Results of Deploying Office 2003 to 1,000 Devices
Table C-1
HTTP Threads
400
300
350
350
300
200
110 System Planning, Deployment, and Best Practices Guide
or
ZENserverw ZENloaderw
/etc/init.d/novell-zenserver
.
file at:
InstallDirectory\Novell\ZENworks\share\tomcat\conf
/opt/novell/zenworks/share/tomcat/conf
HTTPS Threads
200
300
250
200
200
200
from the Run line, then click the Java tab.
or
/opt/novell/zenworks/bin/
file were increased from the
server.xml
Results
Failed
Failed
Failed
Passed
Passed
Passed
Explanation
ZENserver dies. Java
out-of-memory error.
Java out-of-memory
error.
Java out-of-memory
error.
Time: 35-40 minutes,
Client Retries: 15
average. This is the
maximum for HTTP

threads.

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