MapInfo Spatial Server Map Tiling Service - Product Documentation ...

Global Configuration Parameters
10
Parameter
MinIdle
MaxIdle
MaxTotal
ExhaustedAction
Type
integer
integer
integer
string
Required
no
no
no
no
Description
hausted. The default setting for this parameter is
8.
The minimum number of idle offscreen bitmaps
(per tile dimension) that should always be available.
If this parameter is set to a positive number and
TimeBetweenEvictionRunsMills is greater
than zero, each time the idle object eviction thread
runs, it will try to create enough idle instances so
that there will be this number of idle instances
available under each key. The default setting for
this parameter is 0.
The maximum number of offscreen bitmap that can
sit idle in the pool (per tile dimension) at any time.
When negative, there is no limit to the number of
objects that may be idle per key. The default setting
for this parameter is 8.
The global limit on the number of objects that can
be in circulation (active or idle) within the combined
set of pools. When non-positive, there is no limit to
the total number of objects in circulation. When
MaxTotal is exceeded, all keyed pools are exhausted.
When MaxTotal is set to a positive value
and an offscreen bitmap is requested when at the
limit with no idle instances available, an attempt is
made to create room by clearing the oldest fifteen
percent (15%) of the elements from the keyed
pools. The default setting for this parameter is -1
(no limit).
The behavior when the pool of offscreen bitmaps
is exhausted. The options are fail, grow, or block.
Fail will throw an exception when an offscreen bitmap
is requested when the pool is exhausted.
Grow, the default, will create a new offscreen bitmap
and return it, making MaxActive meaningless.
Block will stop the process until a new or idle
object is available.
Optionally, one may configure the pool to examine
and possibly evict objects as they sit idle in the pool
and to ensure that a minimum number of idle objects
is maintained for each key. This is performed
by an idle object eviction thread, which runs asynchronously.
Caution should be used when configuring
this optional feature.
Eviction runs require an exclusive synchronization
lock on the pool. If they run too frequently or incur
excessive latency when creating, destroying or
validating object instances, performance issues
MapInfo Spatial Server 1.0