Document Conversion Service 3.0
Application Factory Settings
will not recycle.
The maximum length of time to wait after the
application has been initialized before Document
Conversion Service initiates communication with
the application. This value may need to be
increased for machines running high volume with
many other applications running.
Some applications need more time than others to
complete their initialization. Enter in the length of
time, in microseconds, to wait for the application to
The amount of time, in milliseconds, to wait before
an idle application is closed and removed from the
application pool. An idle application is one that has
not processed any conversions in the specified
time period. These idle applications are removed
from the pool to free up resources. They are
added back in on demand as needed.
This is set to 3,600,000 milliseconds (1 hour) by
default in the global
If this is set to 0, the applications in the pool will
start dynamically but will not be dynamically
removed from the pool. They will only be removed
if they are recycled due to conversion failure or the
settings for RecycleThreshold,
The size (in 1024KB blocks) at which to recycle
the application. For example, 1400000 is 1.4GB
meaning the application will be recycled when its
virtual size is larger than 1.4 GB. Is it important to
keep this value below the 2GB virtual size for 32-
bit applications. While you can disable the
application recycling based on Virtual Size by
setting this to 0 or removing the value completely,
we do not recommend this.
The maximum number of combined user and GDI
handles allowed for each application instance.
When this number of user and GDI handles
exceed this threshold the application will be
recycled and a new instance started to replace it in
the application pool. If this value is not set, or set
to zero, the maximum number of combined
handles is 8000.
The maximum number of process handles allowed
for each application instance. When this number
exceeds this threshold the application will be