[Zope] Strange TransactionError in ZODB
Harald Koschinski
harald.koschinski@friatec.de
Tue, 20 Feb 2001 17:33:08 +0100
Chris McDonough wrote:
> Do you allow image uploads? Do you use the catalog?
- no upload off images
- I don=B4t use zcatalog
>
>
> If so in either of these cases, subtransction changes in 2.3.1 b1 might=
help
> solve the problem.
>
> It also may be an error in the transaction code in either SQLSession or=
> MySQLDA.
I believe here is the problem - SQLSession and /or MYSQLDA.
So what can I do to get the problem fixed.
>
>
>
> I'd try 2.3.1 final when it comes out. If you're in a hurry, you can t=
ry
> the beta 1 of 2.3.1 which is available on Zope.org.
>
> ----- Original Message -----
> From: "Harald Koschinski" <Harald@koschinski.com>
> To: "Chris McDonough" <chrism@digicool.com>
> Sent: Friday, February 16, 2001 11:28 AM
> Subject: Re: [Zope] Strange TransactionError in ZODB
>
> Chris McDonough wrote:
> >
> > You didn't receive a StorageTransactionError, you received a
> > TransactionError. This is not the same.
> >
> > Are you using a relational database or a sessioning product? If so, =
which
> > ones?
> I am using MySQL as backend for SQLSession 0.3.
>
> >
> > ----- Original Message -----
> > From: "Harald Koschinski" <harald.koschinski@friatec.de>
> > To: <Zope@zope.org>
> > Sent: Friday, February 16, 2001 6:51 AM
> > Subject: [Zope] Strange TransactionError in ZODB
> >
> > Hi,
> >
> > some times my zope 2.2.4 server gives the following error:
> > ---------------------------------------------------------------------=
-----
> --
> > ----------------
> >
> > Zope Error
> >
> > Zope has encountered an error while publishing this=
> > resource.
> >
> > TransactionError
> >
> > Sorry, a Zope error occurred.
> >
> > Traceback (innermost last):
> > File
> > /usr/local/opt/Zope/server/test2/lib/python/ZPublisher/Publish.py, li=
ne
> > 222, in publish_module
> > File
> > /usr/local/opt/Zope/server/test2/lib/python/ZPublisher/Publish.py, li=
ne
> > 187, in publish
> > File
> > /usr/local/opt/Zope/server/test2/lib/python/Zope/__init__.py, line 22=
1,
> > in zpublisher_exception_hook
> > (Object: Traversable)
> > File
> > /usr/local/opt/Zope/server/test2/lib/python/ZPublisher/Publish.py, li=
ne
> > 175, in publish
> > File
> > /usr/local/opt/Zope/server/test2/lib/python/Zope/__init__.py, line 23=
5,
> > in commit
> > File
> > /usr/local/opt/Zope/server/test2/lib/python/ZODB/Transaction.py, line=
> > 208, in commit
> > TransactionError: A serious error, which was probab=
ly
> > a system error,
> > occurred in a previous database
> > transaction. This
> > application may be in an invalid st=
ate
> > and must be
> > restarted before database updates c=
an
> > be allowed.
> >
> > Beware though that if the error was=
> > due to a serious
> > system problem, such as a disk full=
> > condition, then
> > the application may not come up unt=
il
> > you deal with
> > the system problem. See your
> > application log for
> > information on the error that lead =
to
> > this problem.
> >
> > ---------------------------------------------------------------------=
-----
> --
> > -----------------
> >
> > In the documentation I found:
> > ---------------------------------------------------------------------=
-----
> --
> > -----------------
> >
> > ZODB.Exceptions.StorageTransactionError
> >
> > Documentation
> >
> > This exception is raised if a storage method is called in an invalid
> > state. Storages are required to raise this error under certain
> > conditions.
> > Applications should never encounter this exception unless there is a =
bug
> > in ZODB or in a storage implementation.
> > Concurrency
> > sequential
> > Persistence
> > ---------------------------------------------------------------------=
-----
> --
> > -------------------
> >
> > So it look=B4s like a serious error deep down in the ZODB transaction=
> > system.
> > There are no problems on the OS (Linux 2.2.14), no disk full ...
> > The error appears 2 times a week on a live running system with 100000=
> > requests a day. When the error appears the only way to fix it, is to
> > restart the server.
> >
> > Does anybody know the reason for this error?
> > Is there a fix for it??
> > Is it fixed in Zope 2.3.x ??
> > Does DC know the problem, do they fix it?
> >
> > Any help is really appreciated.
> >
> > regards
> >
> > Harald
> >
> > _____________________________________________________________________=
> >
> > FRIATEC Aktiengesellschaft
> > Informationssysteme und Organisation
> > Tel. 0621 - 486 - 1454
> > Fax. 0621 - 486 - 1840
> > Steinzeugstrasse 50
> > mailto:harald.koschinski@friatec.de
> > D-68229 Mannheim
> >
> > _______________________________________________
> > Zope maillist - Zope@zope.org
> > http://lists.zope.org/mailman/listinfo/zope
> > ** No cross posts or HTML encoding! **
> > (Related lists -
> > http://lists.zope.org/mailman/listinfo/zope-announce
> > http://lists.zope.org/mailman/listinfo/zope-dev )
> >
> > _______________________________________________
> > Zope maillist - Zope@zope.org
> > http://lists.zope.org/mailman/listinfo/zope
> > ** No cross posts or HTML encoding! **
> > (Related lists -
> > http://lists.zope.org/mailman/listinfo/zope-announce
> > http://lists.zope.org/mailman/listinfo/zope-dev )
>
> _______________________________________________
> Zope maillist - Zope@zope.org
> http://lists.zope.org/mailman/listinfo/zope
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope-announce
> http://lists.zope.org/mailman/listinfo/zope-dev )
--
Mit freundlichen Gr=FC=DFen
Harald Koschinski
_____________________________________________________________________
FRIATEC Aktiengesellschaft
Informationssysteme und Organisation
Tel. 0621 - 486 - 1454
Fax. 0621 - 486 - 1840
Steinzeugstrasse 50
mailto:harald.koschinski@friatec.de
D-68229 Mannheim