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...Administration ...Administration ...Memory Leak in DNN 441Memory Leak in DNN 441
Previous
 
Next
New Post
3/9/2007 4:39 PM
 
The server in question has 6GB of RAM and Dual Xeon 3.4 GHz and 500GB RAID3 HDD. I am running 2 DNN installations on this server, but the other install is only used for testing puropses, and it is not getting the same errors. An out of memory error should not be happening on this server IMHO.
 
New Post
3/9/2007 6:09 PM
 

You are right, if you are not limiting the memory then you should not get that error.

Have a look at the app pool settings for the memory limit and increase the threshold to see if that helps.

You may also want to look at what other processes on the same machine are using memory.

It's not unusual for DNN to climb to and past 180MB on a single portal, and much higher if you have several portals.


DotNetNuke Modules from Snapsis.com
 
New Post
3/9/2007 9:55 PM
 
I've been following this thread all day and I may have some insight. When you mentioned your hardware configuration, it rang a bell with me.

I encountered the same issue about 18 months with a similarly configured system. I ended up calling in Microsoft Technical Support. Their engineers couldn't figure it out, but wouldn't let go of the issue. After 11 hours, they they finally found it: the second nic was incorrectly configured.

Hope this helps.

Scott
 
New Post
3/10/2007 5:48 AM
 

There is a specific problem with the Blog module and module level caching. Did you by any chance turn on the module cache for the blog module? This might also have happened if you used the "Apply to all modules" option in Module settings from another module that used Module Caching.

Because the page with the blog module cannot be reached anymore, the only thing you can do is to turn off the module cache from within the DB. Also, you can set the module cache to -1 in the blog module module definition, this will prevent the module to be cached as well.


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
3/12/2007 8:25 AM
 
As stated in previous posts in this thread, I do not have a blog or event module. I have checked the memory settings for the application and have set it to recycle itself every six hours, as well as increasing the amount of allowable memory. Hopefully, this will take care of me needing to check on it constantly. Thanks for everyones help.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Memory Leak in DNN 441Memory Leak in DNN 441


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