This message is to be expected when there are no available Web Player instances to load the report.
The queue mentioned in the error message refers to the centralized TIBCO Spotfire Server queue which is managed in the cluster memory. Scheduled update jobs that cannot be immediately run, because all Web Player instances are all loading their maximum number of concurrent updates, are now queued on the TIBCO Spotfire Server for distribution to Web Player instances as they become available. This results in a more robust routing of jobs than seen previously, where each Web Player service maintained its own job queue after its maximum number of concurrent updates was reached. Administrators can still manage the maximum number of concurrent updates per Web Player service with the concurrentUpdates setting in the Spotfire.Dxp.Worker.Web.config file (See the referenced
KB 000028397).
If this error message is seen, then no immediate action is required since the report will load when a slot on a Web Player instance becomes available. If the message is seen too frequently, then it may be required to increase the number of concurrentUpdates on the Web Player services if the Node Managers have sufficient resources to load more reports concurrently. Alternatively, you could add more Web Player instances or decrease the number of reports in Scheduled Updates.
Note: The Spotfire Server queuing feature is enabled by default and can be disabled in the TIBCO Spotfire Server configuration by changing the configuration option "enable-queue" to "false" under the section "scheduled-jobs" as seen below. It is not normally required to modify this setting.
<scheduled-jobs>
<enable-queue>false</enable-queue>
</scheduled-jobs>