Summary: 

There are IIS settings that control how often an application pool gets recycled. When the application pool is recycled, it causes an application 

restart, which means that TI Portal has to perform startup processes like reloading the caches (partner catch, partner filter cache etc.). It also 

means users lose their sessions, causing behavior like search fields returning to default values. Therefore, the frequency of application pool 

recycles should be kept low. Setting IIS application pool recycling properties too aggressively can result in poor performance and random 

errors in TI. 

Error:

In many cases, no error occurs but the user experiences intermittent slowness and lost sessions. Depending on what action the user is 

taking at the time of the application restart, they may see random exceptions that are not consistently reproducible.

(Applies to TI 5.1 only) To verify if you are experiencing too frequent application restarts, start by examining the TI Event Log. Look for 

"Partner Cache Thread" events. If these are happening more frequently then you have specified on the Common 

Admin –> Setttings –> Cache page, you may have set your IIS settings too low.

For further confirmation, or if you don't have TI 5.1, you can turn on ASP.NET Health Monitoring:

1.     Find the root web.config file. This is not provided by TIBCO, it comes with installing .NET. It will be in this directory (customer's may 

be slightly different):  C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config

2.     BACK UP THE WEB.CONFIG FILE!!!

3.     Find the <healthMonitoring> section. Beneath that, find the rules section. Add the "Application Lifetime Events" rule as shown in 

this example:

<rules>

<add name=”All Errors Default” eventName=”All Errors” provider=”EventLogProvider”

profile=”Default” minInstances=”1” maxLimit=”Infinite” minInterval=”00:01:00”

  custom=”” />

<add name=”Failure Audits Default”  eventName=”Failure Audits”

provider=”EventLogProvider”  profile=”Default”  minInstances=”1”

maxLimit=”Infinite”  minInterval=”00:01:00”

<add name=”Application Lifetime Events Default”  eventName=”Application Lifetime Events”  provider=”EventLogProvider”  

profile=”Default”

minInstances=”1”  maxLimit=”Infinite”  minInterval=”00:01:00”  customer=”” />

<add </rules>

4.     Restart IIS and then log in to TI Portal.

5.     Open the Windows Event Viewer and click on Windows Logs –> Application. You should now see an Informational event with the 

message "Event message: Application compilation is starting.".

6.     Try to reproduce the issues in TI Portal. After you've done this a few times, go back to the Windows Event Viewer. Do you see more 

Information events from ASP.NET indicating an application restart?

7.     After testing, put back the original web.config file in the C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config folder.