Web Player restarts with Event ID 5010 and warning: "failed to respond to a ping."

Web Player restarts with Event ID 5010 and warning: "failed to respond to a ping."

book

Article ID: KB0081685

calendar_today

Updated On:

Products Versions
Spotfire Web Player 7.0 and lower

Description

From the Windows Event Viewer - System events, you will see a Warning Event ID 5010 on the Web Player server:
A process serving application pool 'TIBCO Spotfire Web Player 6.5.0 Pool' failed to respond to a ping. The process id was '944'.
 

 

Issue/Introduction

Web Player restarts with Event ID 5010 and warning: "failed to respond to a ping."

Resolution

The default WAS time out is 90 seconds. The time out of 90 seconds is the default because most applications running in IIS do simple tasks, so the response times are supposed to be low. Spotfire performs resource heavy calculations requiring a lot of memory allocation, so 90 seconds can be at times not be sufficient, especially when there are large amounts of RAM (and therefore larger data sets being operated on). There have seen cases during normal operations with large .NET heaps that sometimes lead to garbage collection that can take more than 90 seconds. In these cases, we recommend increasing the time out to better accommodate these long running actions. From the default value of 90 seconds, you can increase the setting to 120, 180, 240, or 300 incrementally until the issue is no longer seen. You do not want to increase the setting too large otherwise IIS will not be able to reset the application in a timely manner in an actual case of a hanging application.

You can update the time out here:

 - IIS -> Application Pool -> Web Player -> Advanced Settings -> Ping Maximum Response Time

See the attached (Filename: IISAppPoolAdvSetting.jpg) picture.

Attachments

Web Player restarts with Event ID 5010 and warning: "failed to respond to a ping." get_app