Team System Developer Center >
Visual Studio Team System Forums
>
Team Foundation Server - Team System Web Access
>
TSWA 2008 SP1 - Work Item Store Exception
TSWA 2008 SP1 - Work Item Store Exception
- We are getting frequent interruptions of TSWA due to the Work Item Store Exception. I know the limitations of TSWA but I am sure our user base it self is around 150Users with many of users accessing Work Items through Visual studio, rather than TSWA leaving a fraction of Business Analysts updating the WI through TSWA. We do have a moderate 900 Active Work Items in one of our Large project which I think is also a real low to hit the limits of TSWA. But still we are getting this every day.
I am trying to see what are the other possible things without inturrupting the user sessions we can avoid Work Item Store exception. I am sure there so many other using TSWA with much more larger activities. Currently we setup to recycle the App Pool at 5AM and 6:30PM every day. I saw sometimes, App pool touching the 2GB sometimes.
Thanks,
Ravi
Answers
- Hi Ravi,
Thanks for reporting this issue.
If you haven't read Team System Web Access 2008 Scalability Limits White Paper, you'd better read it first. It is not recommended to have more than 100 concurrent users for one instance of TSWA.
From the white paper, you can try the following ways to fix the problem:
1. If you have installed VSTS or TFS in same machine with TSWA, you should also apply VSTS SP1 and TFS SP1.
2. Change ASP.NET Cache Memory Settings in web.config
<system.web> <caching> <cache disableMemoryCollection = "false" disableExpiration = "false" privateBytesLimit = "1000000000" percentagePhysicalMemoryUsedLimit = "60" privateBytesPollTime = "00:01:00" /> </caching>
It makes ASP.NET reclaim memory cache more aggressively.
3. Install additional Web Access instance
If none of the other ways work, you can setup another web access server. But it requires that your team use two URL to visit the site.
Hope it helps.
Hongye Sun [MSFT]
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg @ microsoft.com
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.- Marked As Answer byrtandra Tuesday, November 03, 2009 5:12 PM
All Replies
- Hi Ravi,
Thanks for reporting this issue.
If you haven't read Team System Web Access 2008 Scalability Limits White Paper, you'd better read it first. It is not recommended to have more than 100 concurrent users for one instance of TSWA.
From the white paper, you can try the following ways to fix the problem:
1. If you have installed VSTS or TFS in same machine with TSWA, you should also apply VSTS SP1 and TFS SP1.
2. Change ASP.NET Cache Memory Settings in web.config
<system.web> <caching> <cache disableMemoryCollection = "false" disableExpiration = "false" privateBytesLimit = "1000000000" percentagePhysicalMemoryUsedLimit = "60" privateBytesPollTime = "00:01:00" /> </caching>
It makes ASP.NET reclaim memory cache more aggressively.
3. Install additional Web Access instance
If none of the other ways work, you can setup another web access server. But it requires that your team use two URL to visit the site.
Hope it helps.
Hongye Sun [MSFT]
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg @ microsoft.com
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.- Marked As Answer byrtandra Tuesday, November 03, 2009 5:12 PM


