So what could be going on ?
Deadlocks somewhere?
Something appears to be creating immortal
sessions, but forced session termination (by the user logging out)
and
session expiration seem to be behaving themselves.
Can you get a stacktrace of the app? We had things like that with a
deadlocked session's defaultEditingContext. The sessions got stuck
when they
tried to checkout, locking their editingContexts.
cug
If this was happening what would the user see ? Would the app just
behave like the session was dead and send them back to the login page ?
If I ask any of the users if they are having any problems, or noticed
anything strange going on they all say "no, every thing is fine"
I'm wondering if they are actually being "logged out" more often than
they should be because of this error, but they just think it's normal
behavior.
I'll stick in a bunch more logging as Kieran has suggested and see
what we get.
Thanks chaps!
Simon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
