By default, an IIS application pool (or “AppPool”) recycles on a regular time interval of 1740 minutes or 29 hours.
...
Open IIS MANAGER (command: inetmgr)
Go to Application Pool section
right-click TFS4JIRA application pool (default name: TFS4JIRA Sync App Pool)
choose ADVANCED SETTINGS
please set: Start Mode to AlwaysRunning
please set: Idle Time-out (minutes) to 0
click OK to confirm changes
Expand Sites and Default Web SIte (please note: this is default TFS4JIRA installation site, you may have a different configuration)
Right-click TFS4JIRA application (default name: tfs-jira-synchronizer)
go to MANAGE APPLICATION → ADVANCED SETTINGS
please set: Preload Enabled to True
As a final step please restart your site (site where TFS4JIRA application is installed)
WORKAROUND
That situation where Synchronizer stops processing after application pool recycle is the standard behavior of IIS 7.0, not an error or issue. The site only comes into memory on first access and that usually takes longer than subsequent access.
The solution or rather a workaround. is to create a scheduled task on event id 1033 with a simple command:
Code Block |
---|
powershell -Command "Invoke-WebRequest http://localhost:8081" |
running from the SYSTEM account.
Please of course remember to enter your synchronizer address and port.