[ZODB-Dev] [ZODB3.1] easily reproducible deadlock

[Christian Robottom Reis]

On Sat, Dec 06, 2003 at 08:16:44PM -0500, Shane Hathaway wrote:
> >I have an appliciation that (for modularity reasons)
> >opens two separate ZODB connections to the same ZEO server and
> >the same storage. When both connections are affected by a transaction,
> >deadlock occurs when the transaction commits.

[snip]

> We have avoided opening two connections to the same storage for reasons 
> just like this.  It's an artifact of the design.  We'd be pleased to 
> hear a solution for your problem that does not break the design. :-)

Hmm, are we talking about instantiating two *ClientStorages* in-process?

I open multiple connections to the same storage all the time, AFAIUI,
but that's a matter of calling db.open() multiple times.

Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331