Dennis Allison wrote at 2005-11-18 13:15 -0800:
>We are using MySQL but are fully transactional using innodb.
>2005-11-18T12:50:16 ERROR txn.3075 Error in tpc_abort() on manager
>0x450431cc> at 1190763820>
Thus, you should find out why "tpc_abort()" fails on the
"ZMySQLDA.db.DB" instance...
> ..
We are using MySQL but are fully transactional using innodb.
The sort of problems we are seeing are (cruft removed) are things like:
2005-11-18T12:50:16 ERROR txn.3075 Error in tpc_abort() on manager
at 1190763820>
2005-11-18T12:50:16 ERROR txn.3075 Error in tpc_abort() on manager
at 11907742
On Sun, 2005-11-13 at 01:39 -0800, Dennis Allison wrote:
> Zope 2.8.4
> ZEO 3.4.2
> ZODB 3.4.2
> Python 2.4.2 or 2.3.5
> MySQL 4.0.20
> MySQL-Python 1.2.0
> MYSQLDA 2.0.9
>
> We have just moved from Zope 2.7.6 to Zope 2.8.4 motivated, in part, but
> the ability to avoid read conflicts under ZODB
Have you considered upgrading to PostgreSQL? Things might have changed
since the last time I tried mysql but I'm pretty sure Postgresql and
psycopg deals much better with transactions in Zope. Admittedly, this
doesn't explain why you're getting into trouble just because you've
upgraded to zodb 3.4.
Zope 2.8.4
ZEO 3.4.2
ZODB 3.4.2
Python 2.4.2 or 2.3.5
MySQL 4.0.20
MySQL-Python 1.2.0
MYSQLDA 2.0.9
We have just moved from Zope 2.7.6 to Zope 2.8.4 motivated, in part, but
the ability to avoid read conflicts under ZODBÂ 3.4.2. We have been having
a lot of problems: more conflict errors, releas
