|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Session State problems for multiple usersHopefully somebody can help me... (Using Visual Studio 2005, SQL Server 2005, C# and ASP.NET) The development team I work in has created a large application that has started displaying some nasty bugs which we think are being caused by the session state. When a single user logs in, their location ID is assigned to the session state. This location ID persists until the browser session is closed and no bugs appear. However, when another user logs in, using a different location ID, the original user's session state changes to show the new user's location ID! Sometimes, the location ID held within the session state 'swaps' between users e.g. I log on as location 124 and a colleague logs on as location 230 - suddenly, my location is 230 and my colleague's is 124! We have checked to ensure that the session ID persists, it's just the values of the session state that are changed. Any help will be gratefully received :) Thanks, Rob What code are you using to write the location ID to the session state?
Show quote "mcbobin" <mcbo***@gmail.com> wrote in message news:1167754377.380710.322730@a3g2000cwd.googlegroups.com... > Hi, > > Hopefully somebody can help me... > > (Using Visual Studio 2005, SQL Server 2005, C# and ASP.NET) > > The development team I work in has created a large application that has > > started displaying some nasty bugs which we think are being caused by > the session state. > > When a single user logs in, their location ID is assigned to the > session state. This location ID persists until the browser session is > closed and no bugs appear. > > However, when another user logs in, using a different location ID, the > original user's session state changes to show the new user's location > ID! > > Sometimes, the location ID held within the session state 'swaps' > between users e.g. I log on as location 124 and a colleague logs on as > location 230 - suddenly, my location is 230 and my colleague's is 124! > > We have checked to ensure that the session ID persists, it's just the > values of the session state that are changed. > > Any help will be gratefully received :) > > Thanks, > > Rob > |
|||||||||||||||||||||||