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 ...major issue with nCache and DotNetNuke Web Farmmajor issue with nCache and DotNetNuke Web Farm
Previous
 
Next
New Post
3/2/2010 5:26 PM
 

Environment: 
2 web servers with DNN 4.9.5 load balanced by an F5 Big IP with no persistence set
Alachisoft's nCache for keeping sessions in sync
Broadcast Polling
SSL
almost exclusively Telerik controls

We have a major issue in which users are seeing other users' data randomly.  Almost all data calls are SP calls passing in a string derived from a session.

The user will click on page1, and the correct information will be there.  They will click on page2, come back to page1, and have another users'  data.  They can then click on the page1 in the menu, which basically just refreshes the page, and the correct data is displayed again.  

There are also instances where 1 module will have 2 controls, and there will be correct data in one and incorrect data in the other.

This only happens once there are about 200-300 users hitting the servers, or possibly it is after about 25-30 minutes.  Sessions die at 20 minutes so we are looking into that.

We have had nCache on with us for 3 teleconferences, but they have never seen anything similar. 

Has anyone else used nCache with DNN?  

Has anyone seen similar issues even if you don't use nCache?

We would love to go 1 server and inProc, but at this time the client insists on 2 servers.

Thanks for any help you can provide.

Chad

 

 

 
New Post
3/5/2010 10:33 AM
 

The issue was that a junior developer had made all data calls static, and under load this caused the issue.

 

 
New Post
3/5/2010 11:04 AM
 

Chad,

  Can you provide a code example.  It would be very good for community members to see the exact code pattern which exposes this issue so they can avoid it in their own code.

 


Joe Brinkman
DNN Corp.
 
New Post
3/5/2010 11:57 AM
 

Joe,

I just wanted to state that nCache has nothing to do with this issue, and that it is an amazing product. 

We have a middle tier (app_code) and a class for each module.

In the class, we may have something similar to:

public DataSet _specialties;

        public bool PerformGetSpecialties(string id)
        {
            _specialties = SqlProvider.ExecuteSPDataset(Global.GetConnectionName,
                SP_GET_SPECIALTIES, new object[] { Id });
            if (_specialties != null)
                return true;
            else
                return false;
        }

Then in the code behind of the module:

If (classname.PerformGetSpecialties(id)

{

   whatever.datasource = classname._specialties;

}

If that dataset is static, or any other dynamic variable is static, then it is going to cause issues under load.    If it is a call to retrieves states or countries, where the result never changes, then it is fine.

Here is the link that led me to it.

http://blogs.msdn.com/jorman/archive/2005/11/22/users-seeing-other-users-data-in-asp-net.aspx

 

 

 

 

 

 

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...major issue with nCache and DotNetNuke Web Farmmajor issue with nCache and DotNetNuke Web Farm


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