When those transactions are blocking the instance, the browser request
might be redirected to another instance by wotaskd. And that instance
doesn't know about the session and thus reports "session timed out"
while the correct message would be "session not found" in this case.
Maybe this is the case? Then use something like WOLongResponsePage or
ERXLongResponse to pevent the instance from blocking.
Timo
Am 03.02.2010 um 11:13 schrieb Frédéric JECKER:
Hi,
In our application's Session object we set the default session
timeout to 3600 seconds by a call to the setTimeOut() function
within the constructor.
One some specific transactions we lengthen this time by modifying
the user's session (again using the setTimeOut() function).
We have very hazardous issues with those timeouts as sometimes users
are experiencing session loss after only 10 minutes of inactivity.
What are we doing wrong ? are there some good practices regarding
timeout usages ?
Thanks for your help
Regards
Fred
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/th-dev%40onlinehome.de
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
