Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...SocketTimeoutExceptions / W3WP.exe burns out CPUSocketTimeoutExceptions / W3WP.exe burns out CPU
Previous
 
Next
New Post
10/10/2012 9:13 AM
 

Hello,

I'm running DNN CE 6.02.00 with ASP v.4 on a Windows Server 2003 server with MS SQL Server 2008 R2...

These past two or three weeks we've noticed some serious issues with the application pool's worker process (w3wp.exe) for a particular site running up the CPU and eventually taking the site down (and other sites with it as it is a shared environment). These SocketTimeoutExceptions come in spurts, intermittently, and without warning. A dedicated application pool has been set up for each application, however, this one site / appPool has been isolated as the culprit from using Task Manager to get the PID then using inetmgr to tie the PID to an application pool. 

From my limited experience troubleshooting DNN sites, this appears to be the grandaddy of all problems. I've used Windbg, Process Explorer, and DebugDiag to try and make sense of the issue. This doesn't really help, though, because I have no idea how to read the dumps that are tossed out and no real understanding of how application stacks or threads work.

I've opened a ticket directly with Microsoft .NET support to see if they might be able to shed some light on the issue. I've also downloaded ANTS Memory Profiler (http://www.red-gate.com/SupportCenter...) onto the server b/c I've read it's output is easier to understand and make use of. 

From what I can see, it says that memory fragmentation is affecting the size of the largest object that can be allocated. It has also suggested that my application is suffering from fragmentation of the large object heap.

Does anybody have some light to shed on this? I'd greatly appreciate it!

 
New Post
10/10/2012 1:15 PM
 
Please check your Event Log and and Scheduled Task History and clean them if you have a lot of log entries in it.
 
New Post
10/10/2012 1:42 PM
Accepted Answer 
Matthias,

Thanks so much for your reply. I've cleared the logs in both the Event Log and Scheduled Task History.

I guess we'll see if this has a notable effect on the CPU issue that was occurring :)

(Already the site seems to load faster... might be the placebo effect).

Thanks,
Justin
 
New Post
10/10/2012 1:44 PM
 

Matthias,

 Thanks so much! I guess we'll see if that has a notable effect on this issue that keeps intermittently happening...

 The site already seems to be loading faster, although that might be the placebo effect - ha!

-Justin

 
New Post
10/10/2012 3:08 PM
 
Great if my post solves your issue it would be great to click the accepted Answer ;) So the post changed to Status resolved.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...SocketTimeoutExceptions / W3WP.exe burns out CPUSocketTimeoutExceptions / W3WP.exe burns out CPU


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out