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 ...Worker process deadlockingWorker process deadlocking
Previous
 
Next
New Post
1/16/2008 1:55 PM
 

Jerry Andersen wrote

In your host settings, are you writing the event log directly to disk or is it writing to memory then to the database or file?  I had trouble with this because I wasn't writing the log to memory but I had the scheduled PurgeLogBuffer scheduled.  For some reason it didn't like that and you can other topics regarding an issue with the scheduled events causing problems with the portal from 4.7 and up.  If I can find those links I will post them for you.

I hadn't changed these from their default and havn't read much into the schedule issues others were having yet.  I guess I'll have to trust the search more. :)

I did turn off Ajax based on a suggestion somewhere and the crashes seemed to go away, but the Application log is still showing the errors.

 
New Post
1/16/2008 3:50 PM
 

You might also check your application pool settings to ensure that a memory limit isn't set for the app pool that DNN is running in.

Also, if you haven't done so already, enable caching in host settings.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
1/16/2008 4:34 PM
 

Mitch Sellers wrote

You might also check your application pool settings to ensure that a memory limit isn't set for the app pool that DNN is running in.

Also, if you haven't done so already, enable caching in host settings.

If you are referring to memory recycling, it isn't set.

I was planning on googling some on performance settings for DNN at a later date.  I've tested these before and was not encouraged enough to change the default settings in a fairly dynamic environment (lots of users updating their own pages/sub portals). So I've left the defaults--cache to disk and moderate.  Are you referring to a specific setting here?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Worker process deadlockingWorker process deadlocking


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