 |
| ASP.NET 1.0 and 1.1 Basics ASP.NET discussion for users new to coding in ASP.NET 1.0 or 1.1. NOT for the older "classic" ASP 3 or the newer ASP.NET 2.0. |
Welcome to the p2p.wrox.com Forums.
You are currently viewing the ASP.NET 1.0 and 1.1 Basics section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
|
|
|
|

November 12th, 2006, 09:04 PM
|
|
Registered User
|
|
Join Date: Nov 2006
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Quote:
quote:Originally posted by dparsons
Why are you trying to store a Dataset in Session???? IMHO, you shouldn't do this and it may be where you are running into a problem.
When you store stuff in session, specifically when your session state is InProc, that information is stored on the server for the current client thread. (If you fire up task manager on the server the process is called aspnet_wp.exe) Anyway.
This process will can consumer up to 80% of your severs resources before it "recycles" itself and, what I mean by this, once that process has used up 80% of your system's resources, the process crashes and restart's itself. So what?
Since you are storing your session InProc, when this process crashes all of your current session data is lost (application wide) so, I think, that may be the problem you are running into since you said that this application is being used in a corporate environement and you have over 100 users hitting this application. (e.g. you are saving datasets in session which could be consuming a considerable amount or resources)
Lastly, to answer your question specifically, I have never run into an instance where my session variables just disappear and become null (the only time that I can forcibly make this happen, outside of letting my session timeout, is when i create a new build of my application in Visual Studio and then copy it over to my production directory, this causes the application to restart itself, thus my session info is lost)
"The one language all programmers understand is profanity."
|
We are having similar problems; but we don't store alot in the session state. But we do store huge datasets in ASP.NET's cache to increase performance. Does this get counted in the 80% resource usage? Customer's sessions keep disappearing and their carts emptying at random, and we lose alot of business from this. Everything points to having the ASP.NET session ID changing at random on us.
|
|

November 13th, 2006, 11:24 AM
|
|
Wrox Author
|
|
Join Date: Oct 2005
Posts: 4,104
Thanks: 1
Thanked 64 Times in 64 Posts
|
|
Possibly. What you should probably do, in a test environment, is have a bunch of your developers hit the application and load things into carts and such while someone monitors the aspnet_wp.exe process on the server. If you see that it begins to consume large amounts memory yes this is your problem.
Also, after your done testing and everyone logs off, check to make sure that the memory the the process consumed is actually released back to the server.
-------------------------
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.
^^Thats my signature
|
|

November 13th, 2006, 01:46 PM
|
|
Friend of Wrox
|
|
Join Date: May 2006
Posts: 643
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Quote:
|
quote:Originally posted by dguisingerWe are having similar problems; but we don't store alot in the session state. But we do store huge datasets in ASP.NET's cache to increase performance. Does this get counted in the 80% resource usage? Customer's sessions keep disappearing and their carts emptying at random, and we lose alot of business from this. Everything points to having the ASP.NET session ID changing at random on us.
|
I don't think the session is changing at random without a good reason. For example, perhaps they are timing out.
Woody Z http://www.learntoprogramnow.com
|
|
 |