Problems maintaining Session state

[Sergey Poberezovskiy]

Hi,

I have an ASP.Net application running on a web farm. I
use SessionState = "StateServer" and cookieless mode and
session Timeout = 20 mins.
This is a testing application where a user will be
sitting a number of tests for about one to two hours.
At any given time there could be up to 50 simultanious
users - not a huge load.

the problem is that every now and then the session
objects gets lost - I check the Session("User_Id") on
every Page_Load in order to proceed - and at some point
this becomes Nothing...
On subsequent logins it still works for some time - and
then becomes Nothing again.

Could anyone please help, or suggest what could
potentially be a problem?

Thanks in advance.

 

[Sachin Kharsani[MSFT]]

Hi,
How are you simulating the 50 users? Are they real life users? Or are you
using a Stress tool. If you are using a stress tool then how do you ensure
that all sessions are sending requests and not just one session . Maybe the
catch is here. Neways we can look into this ...Let me know the details.

Regards
Sachin Kharsani


--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
This posting is provided "AS IS" with no warranties, and confers no rights.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-

 

[Sergey Poberezovskiy]

I have not even got to that stage - 50 users is going to
be when the application goes live...
At the moment I am struggling even with 1 or concurrent
users - and the biggest concern is that it's not
consistant:
About a week ago we did about six tests - without a
hickup, and when we asked the client to test it - it
failed three times in a row...

 

[M]

I have come accross a similar situation where session variables are getting
lost temporarily but come back again if user reloads the same page.

Found that whenever the server has to load/compile (not sure which) the
website dlls (for eg the first time a page is requested from a website) and
if the browser makes a subsequent request for another page (for eg the first
page contains an iframe) then the session variables are not visible in the
second page. Strangely the session variables become visible if the browser
re-submits the request. Normally the compile/load process only happens the
first time a page is accessed but our virus scanner appears to be amending
some file in the website (web.config perhaps) and so the web server
re-loads/re-compiles the dll's quite frequently.

We have got around this by not using an iframe in the offending page and
excluding the website directory (for now) in the virus scanner.