[ZODB-Dev] [ zodb-Bugs-550246 ] ClientStorage Deadlock problem
noreply@sourceforge.net
noreply@sourceforge.net
Mon, 29 Apr 2002 12:15:38 -0700
Bugs item #550246, was opened at 2002-04-29 16:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=115628&aid=550246&group_id=15628
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Chris Withers (fresh)
>Assigned to: Jeremy Hylton (jhylton)
Summary: ClientStorage Deadlock problem
Initial Comment:
Shane helped me get to the cause of this on #zope...
<hathawsh> The real problem is that if you have multiple ClientStorages that point to the same
storage on the server, and two or more are involved in the same transaction, a deadlock happens.
This is a pattern that would be very useful to me, it currently causes the storage servers and any
clients connection to them to hang on get_transaction().commit() until they've _all_ been
restarted...
cheers,
Chris
----------------------------------------------------------------------
>Comment By: Jeremy Hylton (jhylton)
Date: 2002-04-29 19:15
Message:
Logged In: YES
user_id=31392
This could be really hard to fix... I don't see a
principled way for a ZEO to know that multiple clients are
part of the same transaction. Maybe the transaction object
can grow some metadata.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=115628&aid=550246&group_id=15628