Server Settings section
The Server Settings section lets you manage client and memory variables, mappings,
charting, and archiving. You also configure mail and Java settings in this section.
Settings page
The Settings page of the ColdFusion Administrator contains configuration options that
you can set or enable to manage ColdFusion MX. These options can significantly affect
server performance. The following table describes the settings:
Setting
Limit simultaneous
requests
Timeout requests
after [n] seconds
Use UUID for
cftoken
Enable Whitespace
Management
Missing Template
Handler
Site-wide Error
Handler
Caching page
The Caching page of the Administrator contains configuration options that you can set
or enable to cache templates, queries, and data sources
affect server performance. The following table describes the settings:
Setting
Template cache size
(number of
templates)
Description
Enter a number to limit simultaneous requests to ColdFusion MX.
When the server reaches the limit, requests are queued and handled
in the order received. Limiting the number of simultaneous requests
can improve performance.
Enable this option to prevent unusually lengthy requests from using
up server resources. Enter a limit to the time that ColdFusion MX
waits before terminating a request. Requests that take longer than
the timeout period are terminated.
Specify whether to use a universally unique identifier (UUID), rather
than a randon number, for a cftoken.
Enable this option to compress runs of spaces, tabs and carriage
return/line feeds. Compressing whitespace can significantly
compact the output of a ColdFusion page.
Specify a template to execute when ColdFusion MX cannot find a
requested page.
Specify a page to execute when ColdFusion MX encounters an error
while processing a request.
Description
Enable this option to limit the memory reserved for template
caching. For best performance, set this to a value that is large
enough to contain your application's commonly accessed
ColdFusion pages, yet small enough to avoid excessive reloading.
You can experiment with a range of values on your development
server; a suitable starting point is one page per MB of JVM size.
.
These options can significantly
Server Settings section
9