Session Woes
-
We're running asp.net 1.1 on iis 6.0 and we're running into all kinds of problems with our in proc sessions. Last week we had a user that actually had an element another users shopping cart and it did not contain what the user had entered. This week we had two orders come thru with 0 items due to dropped session. The users assured us that they had not been on the website for the alloted session timeout. Nothing changed programmaticly for this section of our site. Any Idears?
-
We're running asp.net 1.1 on iis 6.0 and we're running into all kinds of problems with our in proc sessions. Last week we had a user that actually had an element another users shopping cart and it did not contain what the user had entered. This week we had two orders come thru with 0 items due to dropped session. The users assured us that they had not been on the website for the alloted session timeout. Nothing changed programmaticly for this section of our site. Any Idears?
crazidiamond wrote:
we had two orders come thru with 0 items due to dropped session.
This shows your programs loop holes. Don't you validate all these before an order is placed ? What is your actual problem here ? How you are storing shopping details in session ?
-
crazidiamond wrote:
we had two orders come thru with 0 items due to dropped session.
This shows your programs loop holes. Don't you validate all these before an order is placed ? What is your actual problem here ? How you are storing shopping details in session ?
I was handed an amazingly sloppy site. I've been correcting pieces of it as I go along but their aren't enough hours in the day. Since this issue came up I added some logic to determine if in fact the cart is populated. but the bigger problem is that we show no errors when users are placing items into the cart which is stored in "in proc session" and then at a later time we try to access the session contents and the session is not present. We have a Serializable Cart class and we stored the class instance in session. We also determined that the session was not dropped due to timing out. I'm at a loss...