Versions Compared

Old Version 2

changes.mady.by.user Damian Kilkowski (Inactive)

Saved on

compared with

New Version 3

changes.mady.by.user Damian Kilkowski (Inactive)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

By default, an IIS application pool (or “AppPool”) recycles on a regular time interval of 1740 minutes or 29 hours.

...

  1. Open IIS MANAGER (command: inetmgr)

  2. Go to Application Pool section

    1. right-click TFS4JIRA application pool (default name: TFS4JIRA Sync App Pool)

    2. choose ADVANCED SETTINGS

    3. please set: Start Mode to AlwaysRunning

    4. please set: Idle Time-out (minutes) to 0

    5. click OK to confirm changes

  3. Expand Sites and Default Web SIte (please note: this is default TFS4JIRA installation site, you may have a different configuration)

  4. Right-click TFS4JIRA application (default name: tfs-jira-synchronizer)

    1. go to MANAGE APPLICATION → ADVANCED SETTINGS

    2. please set: Preload Enabled to True

  5. 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.