Dated: September 8, 2004
Win6 faced intermittent ASP/ASP.NET issues during peak time yesterday. Since then, our entire technical team has been working on Win6 to resolve some of the intermittent issues this server has been facing in the last 2 or 3 weeks.
What seems to be happening is during peak hours, a certain web application that has been badly coded is causing either .NET or ASP to crash and die. The problem got particularly worse yesterday and our team worked hard to minimize any downtime by the issue yesterday. Since then, our team has been working on Win6 making various configuration changes during the night while most of you slept. There have been a few reboots during this period. The following have also been done
- ASP.NET is now configured to recycle when it approaches its stress levels
- A IIS monitoring service has been installed that monitors ASP and memory usage. If ASP appears to be dead, the service takes corrective measures
Both these changes are temporary measures put in place to prevent downtime from occuring while we try to trace down the problematic site. Currently, a development team is setting up a script on our server to monitor individual asp and asp.net applications to help us determine which site may be causing these issues.
I'd like to assure our customers that we at JodoHost have only the very best people working and managing our servers. Our head windows administrator is an invidual with 7 years of industry experience and who is a MCSE and MCP. We are hoping to return Win6 back to 100% very soon.
We also request cooperation from our customers. if you feel your code may have a memory leak or may be causing any sort of problems on the system, we request you inform us and revise your code. If we do determine your site to be problematic, at best we will shift it to an isolated server till you correct the issue
We thank our customers for their continuing cooperation.
Edit (Added September 20, 2004):
All these issues have comprehensively been resolved. There has been not a single minute of outage in the last two weeks on Win6.
Win6 faced intermittent ASP/ASP.NET issues during peak time yesterday. Since then, our entire technical team has been working on Win6 to resolve some of the intermittent issues this server has been facing in the last 2 or 3 weeks.
What seems to be happening is during peak hours, a certain web application that has been badly coded is causing either .NET or ASP to crash and die. The problem got particularly worse yesterday and our team worked hard to minimize any downtime by the issue yesterday. Since then, our team has been working on Win6 making various configuration changes during the night while most of you slept. There have been a few reboots during this period. The following have also been done
- ASP.NET is now configured to recycle when it approaches its stress levels
- A IIS monitoring service has been installed that monitors ASP and memory usage. If ASP appears to be dead, the service takes corrective measures
Both these changes are temporary measures put in place to prevent downtime from occuring while we try to trace down the problematic site. Currently, a development team is setting up a script on our server to monitor individual asp and asp.net applications to help us determine which site may be causing these issues.
I'd like to assure our customers that we at JodoHost have only the very best people working and managing our servers. Our head windows administrator is an invidual with 7 years of industry experience and who is a MCSE and MCP. We are hoping to return Win6 back to 100% very soon.
We also request cooperation from our customers. if you feel your code may have a memory leak or may be causing any sort of problems on the system, we request you inform us and revise your code. If we do determine your site to be problematic, at best we will shift it to an isolated server till you correct the issue
We thank our customers for their continuing cooperation.
Edit (Added September 20, 2004):
All these issues have comprehensively been resolved. There has been not a single minute of outage in the last two weeks on Win6.