Lack of available Spotfire Web Player instances (all are "exhausted")

When all the Spotfire Web Player instances are exhausted, analysis files cannot be updated according to schedule.

Possible Cause

If this problem is a result of a temporary spike in activity rather than a long-term issue, then you can temporarily disable the CPU exhausted limit. For instructions, see Temporarily disabling the CPU exhausted limit. Make sure to enable the limit again when the spike is finished.

Note: The memory exhausted limit is high by default. It can be disabled too if needed, but this is riskier.

Resolution

Try these adjustments in the following order.

Increase the number of backend connector threads. See Backend connector threads.
Increase the attachment manager cache. See Attachment manager cache.
Increase the database connection pool size. See Database connection pool size.
Add additional Web Player instances to the existing resource pool. See Adding resources to resource pools.
Note: Avoid adding more instances than are needed for the number of users. Data sharing and other internal data structures are most efficient when users share the same analysis on the same service instance.
Increase the scheduled updates concurrency for the affected Web Player instances (the default is 2).
To increase the scheduled updates concurrency:
1. Export and open for editing the file Spotfire.Dxp.Worker.Web.config.
2. Find and change the property concurrentUpdates. For more information, see Manually editing the service configuration files.