[Zope] Re: session variables in the presence of conflicts

[Dennis Allison]

That was my conclusion long ago, but I have not been able to track it
down.  It only occurs under heavy load when backing out of a conflict
error.  I have not been successful at creating a test set that triggers 
it.

I suppose it is time to again read the ZMySQLDA code...   There are a few 
comments on the net about problems with MySQLDA which may also be related.


On Sun, 20 Nov 2005, Florent Guillaume wrote:

> Dennis Allison wrote:
> > Florent,
> > There were, of course, tracebacks.  Any assist you can provide would be 
> > appreciated.   -D
> > 
> > ------
> > 2005-11-18T12:50:16 ERROR txn.3075 Error in tpc_abort() on manager <MultiObjectResourceAdapter for <Products.ZMySQLDA.db.DB instance at 0x450431cc> at 1190763820>
> > Traceback (most recent call last):
> >   File "/usr/local/src/zope/Zope2.8/lib/python/transaction/_transaction.py", line 462, in _cleanup
> >     rm.tpc_abort(self)
> >   File "/usr/local/src/zope/Zope2.8/lib/python/transaction/_transaction.py", line 548, in tpc_abort
> >     self.manager.tpc_abort(txn)
> >   File "/usr/local/src/zope/Zope2.8/lib/python/Shared/DC/ZRDB/TM.py", line 64, in abort
> >     try: self._abort()
> >   File "/opt/zope/zproducts/standard/ZMySQLDA/db.py", line 389, in _abort
> >     self._tlock.release()
> > error: release unlocked lock
> 
> Well undoubtedly the bug is in ZMySQLDA...
> 
> Florent
> 
> 
> 

--