hm... well, maybe I was a bit too worried and premature in my judgement of this error. We have several problems in our app right now, and when this error suddenly started appearing it figured something wird was going on - we are having re-occurring problems with zope dumping core several times a day and it giving s strange errors and tracebacks, and I put this in connection with that. However, each time we get a maximum recursion error (which I am tryong to track down why) it is connected with a setstate error.
The crashes might be connected to a bug found in Python that will be fixed in 2.1.2 and a bug found in Zope 2.4.X (actually in the Restriced Python package). The combination of Zope 2.4.4 (forthcoming, I believe) and Python 2.1.2 (in rc1 state right now) might help things. Of course the symptoms you see might be totally unrelated too. ;-)
When we get it, we don't get only one entry, we get lots and lots and lots of them occurring at the same time. I was watching the stupid log file with tail -f and the ouput wnet on for like 4 seconds.
I'm not sure what this is.