Our Metastorm server sits on a BIGIP F5 load balancer that connects to several Metastorm frontends. We notice that when we connect t the main URL, the to-do list often do not update. The list is correct if we go directly to the individual frontend instead of the load balancer.
At first, we thought it was because one of our server was not working and the load balancer redirecting us to the bad server, but the to-do list was correct on all frontends. We IISreset and reboot all 3 server, remove it from the load balancer and add them back in. Close our browser and relogin. Nothing worked.
We talked with the load balancer's admin and he indicated that the load balancer does not cache any content.
The issue appears to be due to the browser setting. By default, IE is set to check for new content - automatic. What appears to be happening is that when you set the setting to automatic, it will initially check for new content if you change sessions, but the more you use the URL, the less often it checks for new content. Because we use that URL a lot, it was probably not checking if there was new content. When we change the setting to always check for new content or clear our browser cache, the to-do list displayed properly.
The problem is deployment. Now that we know this is the cause of the issue, how can we deploy SR3 and force IE to read the new content? We cannot realistically get everyone to clear their browser cache.