lyptus
asked on
IIS connection strings, application pools.
I have a website that will connect to a different database depenedent on who logs in. So if customer A logs in it sets the connetion string to Customers A's db. If Customer B logs in it sets the connection string to customer B's db. Each customer goes to their own virtual dir. Customer A will go to www.site.com/customerA and customer B will go to www.site.com/customerB. each virtual dir is also running in it's own application pool. based on whe virtual directory they are in, when login is clicked we go to a customer db and look up the connection string for that virtual directory. we then set the connection string in the dataclass to the connection that we get from the customer db. This has seemed to be working. We have certain screens that auto refresh every 60 secs to show any new data. Today we had a customer call and say they were seeing other customers data when the page would auto refresh. after another refresh it would go back to their data. I doesn't happen everytime either. They said it happened once and then happened again an hour or so later. Is there a flaw in our design? Is there something I can do to figure this out? Should I do something entirely different? Thanks for your help.
Ted Bouskill
Hmm, did you create multiple application pools or different application names for each virtual directory? The 'Create' button on the virtual directory doesn't create a new application pool. It creates an application name but that is not an application pool. Many applications can run within one application pool but they will share memory.
ASKER
I did create a new application pool for each virtual directory. I created them under the application pool directory and then set each virtual directory to it's own application pool in the properties of the virtual directory.
Hmm. I wonder if it's a cookie problem that. Are you using cookies to manage your sessions?
ASKER
I think we found the problem. It had to do with the cache. Someone had been looking at another account on this computer. The data it was showing was not live data. So I assumed it was pulling the page from the cache memory. We deleted all temp internet files and we haven't seen the problem again, so far. Knock on wood.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.