Thanks for your answer. Yes I was using cookies but I'm trying now without cookies and I have the same problem. I don't think it's caused by other errors.
I'm wondering if there would be a solution for point 2 making a strong relationship between a user and a session. I mean to have a kind of dictionary with user as key and session as value. Then, because I have the user in the request header, I could look into the dictionary for an existing session for that user and return THE session of the user and avoid creating multiple sessions for one user ? What do you think ? Dominique On Sep 17, 2012, at 7:43 PM, Chuck Hill <[email protected]> wrote: > Hi Dominique, > > Does your application store the session ID in cookies? Are you sure it is a > session timed out and not some other error? If so, here are two things that > can cause this: > > 1. Malformed HTML - some browsers (IE was bad for this) can send another > request to the server when processing invalid HTML (they interpret something > as being a server resource they need to download. The URL they use is not a > valid WO url which causes a new session to get created and the cookies from > this session replace those from the user's real session. > > 2. Multiple Sessions - this seems more likely to me as you mentioned "the > user open many tabs in the browser". If they create a new session in one of > the tabs, the cookies form this session replace those from the user's other > session. When they go back to an earlier tab and click on a button or link, > they get an error as those links are not valid in the new session. > > It could also be that an instance is taking too long to respond and the > user's request is getting sent to a different instance which of course won't > have the user's session. > > > Chuck > > > > On 2012-09-14, at 6:52 AM, Schoenenberger Dominique wrote: > >> I have a problem with untimely session timeout. The user is doing actions >> with the application but suddenly after doing something (a click on a button >> for example), he got a session timeout. >> >> The probability of this to occur is quite low but very annoying for the user. >> >> I suspect that it occurs when the user open many tabs in the browser (?) >> >> Could it be related to a web page having xhtml validation errors ? >> >> Thanks for any help, >> >> Dominique Schoenenberger >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net >> >> This email sent to [email protected] > > -- > Chuck Hill Senior Consultant / VP Development > > Practical WebObjects - for developers who want to increase their overall > knowledge of WebObjects or who are trying to solve specific problems. > http://www.global-village.net/gvc/practical_webobjects > > > > > > > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
