locked
sharepoint server 2007 .net CLR exceptions too high cause server out of memory RRS feed

  • Question

  • shareapoint 2007 : MOSS sp2 with 4 WFE server

    windows 2003 sp2 , .net framwork 3.5sp1 (with kb953595 , 2416473 , 958484 , 963707)

    .net CLR exceptions too high cause server out of memory and the impact is user unable to download large file (when the .net clr exceptions is very high)

    work around is recycle the application pool then is work again then the .net CLR exceptions drop to zero and increase again can up to 30k above.

    we have 2 share point web application , another one is working fine with the .net clr exceptions low and stable.

     

    how do make the exception stable ? 


    sin peow nspsharing.blogspot.com
    • Moved by Lily Wu Tuesday, March 15, 2011 1:48 AM MOSS 2007 issue. Thanks. (From:SharePoint 2010 - General Questions and Answers)
    Tuesday, March 8, 2011 12:26 PM

Answers

  • Conclusion:

    The server’s out-of-memory issue was caused by the workload. So far we don’t find a program that leaked memory.

    Suggestion:

    The memory bottleneck is a popular issue for 32 bit server. With the increase of users and data amount, the 32 bit server’s 4GB can be insufficient to meet the business requirement. The best solution is to upgrade to 64 bit server. If you have customization application that must run in 32bit environment, then you can add more servers into the SharePoint farm and introduce load balance to share the workload between the servers.


    sin peow nspsharing.blogspot.com
    • Marked as answer by Sin Peow Thursday, March 17, 2011 11:27 AM
    Thursday, March 17, 2011 11:20 AM

All replies

  • Do you have many custom solutions installed and are those coded according to best practices?
    My blog on WSS / MOSS development is found at http://jebass.blogspot.com
    Tuesday, March 8, 2011 12:47 PM
  • what exact exceptions you are talking about? Exception handling is resource consuming process, so in order to make "exceptions stable" you need to understand the reasons of these exceptions and remove it from your environment/code.
    Blog - http://sadomovalex.blogspot.com
    CAML via C# - http://camlex.codeplex.com
    Tuesday, March 8, 2011 3:32 PM
  • we have few custom solution installed long time ago, but recently only happen last 2 month :(.

    anyway thanks for the reply , is working with Microsoft to find out which "solution" is causing the .net CLR exceptions and cause the platform facing out of memory.  


    sin peow nspsharing.blogspot.com
    • Marked as answer by Lily Wu Tuesday, March 15, 2011 1:47 AM
    • Unmarked as answer by Sin Peow Thursday, March 17, 2011 11:27 AM
    Monday, March 14, 2011 11:12 AM
  • Conclusion:

    The server’s out-of-memory issue was caused by the workload. So far we don’t find a program that leaked memory.

    Suggestion:

    The memory bottleneck is a popular issue for 32 bit server. With the increase of users and data amount, the 32 bit server’s 4GB can be insufficient to meet the business requirement. The best solution is to upgrade to 64 bit server. If you have customization application that must run in 32bit environment, then you can add more servers into the SharePoint farm and introduce load balance to share the workload between the servers.


    sin peow nspsharing.blogspot.com
    • Marked as answer by Sin Peow Thursday, March 17, 2011 11:27 AM
    Thursday, March 17, 2011 11:20 AM