Chris McDonough wrote:
OK, thanks John.
Thank you for helping.
I hate to ask this (I should have done this to start with), but would
you be willing to use the following patch --against the original file,
not your recently patched version-- and try again? I only checked one
of the two
Although I'm not an expert on _p_independent, AFAIK, it can only be used for
objects which are not in any way dependant on the state of other persistent
objects.
This is certainly not the case for BTrees, which is pretty much covers the
data structures used for cataloguing and indexing.
I
OK, thanks John. Let's try one more thing... currently the mounted
database used to store the session data uses a connection that ignores
read conflicts. This is known to be bad because the machinery which
deals with keeping the sessioning index data will also ignore read
conflicts, which may
Is a PUT_factory allowed to return an object with a different id than
the requested one? Currently NullResource.PUT doesn't cope with that.
But in CMF an object factory is allowed to change the id from the
requested one, so I'm wondering what could happen, and what's best.
Florent
--
Florent
Sorry for the length of this one... but I'm trying to braindump to give you
as much info about the problem as possible.
To be sure it doesn't get lost in my below ramblings, there is probably
important peice of information I haven't mentioned yet... that is that
these errors seem to coincide
John Eikenberry wrote:
Once you start a second thread ReadConflictErrors start getting raised.
Which thread gets the conflict and which one keeps working seems variable
(probably just a timing thing). If I start enough of these threads I can
cause the error to happen. But only once the
