OK, that was fast. I was able to repeat it. Now... let me ask the five million dollar question. ;-) Since SESSION *is* the session data object, why do you want to be able to call getSessionData() on it reliably? I will work on seeing how the wrapping differs between cases, but this may be a feature and not a bug. - C Brad Clements wrote:
On 13 Feb 2002 at 10:01, Chris McDonough wrote:
One thing to try here is to get into the Zope debugger to delete the offending hook and the session data manager that caused it:
I don't think the hook was the problem. The symptons are
1. The REQUEST.SESSION instance has a getSessionData() method only if the server has been restarted without a session_data_manager instance.
That is, if the server is working, then I restart it, then REQUEST.SESSION won't have a getSessionData() method. However if I delete /session_data_manager and restart, it then works again.
2. But worse, it seems that after about 20 minutes ( the default timeout for the storage object), the same problem appears. SESSION loses the getSessionData() method once the timeout specified in /temp_folder/session_data has expired.
--
My client was really upset, so I couldn't experiment any longer. My solution was to remove the 2.5 provided Session product and install CST 0.9. It's working now.
--
Naturally I'd still like to figure this out, how can I help diagnose this? I think it's the transient storage container..
Brad Clements, bkc@murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax netmeeting: ils://ils.murkworks.com AOL-IM: BKClements
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"