Session state issue

[Guest]

Hi,

I'm using .net 1.1. I have ASP.Net appl, shopping cart ,with dataset on
sesion. Dataset here to store all selected items, sesion timeout 120 mins.

Problem is, I got report that: user A select 5 items then close browser,
other user B go to the website it will show 5 items directly. More over user
B is not using same PC, not on same network, reported from different country,
incredible report..

How can this happened, any idea? Could it be becuase non unique session id,
how to prevent?

Thanks a lots,
Martin Adhie N.

 

[Juan T. Llibre]

Probably because you're storing something in the application object,
where it's available to all users, instead of in the session object.

 

[Guest]

Hi Juan,

For sure I didn't put anything on application object. session state
cookieless=false. Confirm that session is unique for PC and browser (some
condition will re-use session id for browser). Is it too long session expired
(120mins), so will generate duplicated sessionid.

Thanks, Martin

 

[Terry Burns]

It's not getting these values by accident. You must have code in there which
is storing and retreiving these values, or else your report is I suggest to
be suspected.

 

[NSS_Wizard]

Martin,

Have you resolved you session state issue, we seem to be encountering the same problem?

Our application is written in VB.Net and runs on a server with the .Net 2.0 SP1 framework but as a .Net 1.1 application. This is our service bureau environment; multiple client organizations. We have also installed this application on in-house servers of other clients for internal use only. The application uses session state to house information between postbacks. Application state is never used. Because we don't want to leave anything on client machines, cookieless="true".

We had a similar (non-unique session ID) situation occur on an in-house install. For want of a better description, the server was viewing all requests to our application as coming from one logical machine. This was how their IT folks installed the server. We were able to resolve this problem by going cookieless="false". But we could in this environment.

In our service bureau environment, we can't do this.

If you have any thoughts to share, different things we should look at, it would be appreciated.

Thanks in advance.

Roger Hodgkiss
NSS Corp