Troubleshooting Spotfire Server
Before diving deeply into logs or contacting support, you can perform some basic steps to check where problems might exist.
Before you begin
Procedure
What to do next
If none of these steps solve the problem with Spotfire Server, review all of the logs and consider creating a troubleshooting bundle for Spotfire Support to analyze. See also Contacting support.
- Spotfire Server fails to start
If the Spotfire Server fails to start, check the log for the error described in this topic. - Spotfire Server runs out of JVM memory
If the Spotfire Server runs out of JVM memory, Spotfire Server can fail or stop responding. This failure can make new connections impossible, and opening any files can fail. - Users cannot log in
Two conditions can cause users to not be able to log in to Spotfire Server. The causes and resolutions for these problems are described in this topic. - CPU usage is very high
If the level of CPU use is very high, the response times typically become longer for the end user, but the system still works. - 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. - Apache Ignite troubleshooting and tuning
Spotfire Server uses Apache Ignite for server cluster management. Property settings can help you manage such concerns such as cluster robustness and how quickly problems are reported. - Significant queue for Information Services jobs
If an Information Services job cannot join the queue, the end user receives an error. - Many concurrent, long-running Information Services jobs
If Information Services cannot retrieve a connection within the configured timeout (the default is 10 seconds), the end user receives an error. - Image rendering time reaches its maximum
When an image is not displayed within the allotted time, and an error is displayed instead of the image. - Attachment manager disk cache is subject to a Least Recently Used (LRU) Eviction
When the attachment manager disk cache is full, the system deletes the least recently used data to make space for new data. - Scheduled updates disk cache reaches maximum size
When the scheduled updates disk cache reaches its maximum capacity, jobs can take longer to finish, or they can fail. - Web Player CPU usage is very high for a long period of time
If the level of CPU usage is very high (above 80%), then the response times typically become longer for the end user, but the system still works. - More Automation Services jobs are trying to run concurrently than the current configuration allows
If you have a lot of Automation Services jobs, and you need them to run concurrently, ensure that the configuration allows the load you require.
- Spotfire Server fails to start
If the Spotfire Server fails to start, check the log for the error described in this topic. - Spotfire Server runs out of JVM memory
If the Spotfire Server runs out of JVM memory, Spotfire Server can fail or stop responding. This failure can make new connections impossible, and opening any files can fail. - Users cannot log in
Two conditions can cause users to not be able to log in to Spotfire Server. The causes and resolutions for these problems are described in this topic. - CPU usage is very high
If the level of CPU use is very high, the response times typically become longer for the end user, but the system still works. - 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. - Apache Ignite troubleshooting and tuning
Spotfire Server uses Apache Ignite for server cluster management. Property settings can help you manage such concerns such as cluster robustness and how quickly problems are reported. - Significant queue for Information Services jobs
If an Information Services job cannot join the queue, the end user receives an error. - Many concurrent, long-running Information Services jobs
If Information Services cannot retrieve a connection within the configured timeout (the default is 10 seconds), the end user receives an error. - Image rendering time reaches its maximum
When an image is not displayed within the allotted time, and an error is displayed instead of the image. - Attachment manager disk cache is subject to a Least Recently Used (LRU) Eviction
When the attachment manager disk cache is full, the system deletes the least recently used data to make space for new data. - Scheduled updates disk cache reaches maximum size
When the scheduled updates disk cache reaches its maximum capacity, jobs can take longer to finish, or they can fail. - Web Player CPU usage is very high for a long period of time
If the level of CPU usage is very high (above 80%), then the response times typically become longer for the end user, but the system still works. - More Automation Services jobs are trying to run concurrently than the current configuration allows
If you have a lot of Automation Services jobs, and you need them to run concurrently, ensure that the configuration allows the load you require.
Parent topic: Basic troubleshooting
Related concepts
Related tasks
Related information