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 ...Weird Portal Cacheing problem...Weird Portal Cacheing problem...
Previous
 
Next
New Post
3/5/2007 12:42 PM
 

Thanks for the response John, but that was not it.  We are definitely only running one process per application pool.

We are however running a separate application pool per portal, for a little load balancing.  Do you think that would be the same effect as the web garden and that might be my problem?

Thanks!

 
New Post
3/5/2007 12:56 PM
 

If there is only one App Pool per for the Portal you are having trouble with then no.

I'm not sure I understand how you could do one App Pool per portal though, do you mean one App Pool per DNN Instance /IIS website?

Also, having multiple App Pools can provide more stability for different instances, but I don't know of any way you could load balance a single instance using App Pools.

If you are really load balancing a single instance by using more than one App Pool for the same site then yes, that would be the problem.

 


DotNetNuke Modules from Snapsis.com
 
New Post
3/5/2007 1:11 PM
 

Hey John,
  Was going by this:
http://www.smallbizserver.net/Default.aspx?tabid=285&EntryID=82

I might have misunderstood that they were talking about multiple installs of the DNN application.

Do you think that might be my problem?  All portals should be using the same APP_Pool?

Thanks!

 
New Post
3/5/2007 2:03 PM
 

Yes, in that setup you will expierence the caching problems that started this thread, especially since she is saying to use more than one web process per app pool.

That setup has two different App Pools pointing to the same DNN Instance.  Since they are in seperate processes they will cache the pages seperately.

It will work for a pseudo load balancing, as long as you are ok with waiting on the cache to "catch up".


DotNetNuke Modules from Snapsis.com
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Weird Portal Cacheing problem...Weird Portal Cacheing problem...


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