[Zope] Strange TransactionError in ZODB

[Chris McDonough]

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?

----- 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, line
222, in publish_module
                    File
/usr/local/opt/Zope/server/test2/lib/python/ZPublisher/Publish.py, line
187, in publish
                    File
/usr/local/opt/Zope/server/test2/lib/python/Zope/__init__.py, line 221,
in zpublisher_exception_hook
                      (Object: Traversable)
                    File
/usr/local/opt/Zope/server/test2/lib/python/ZPublisher/Publish.py, line
175, in publish
                    File
/usr/local/opt/Zope/server/test2/lib/python/Zope/__init__.py, line 235,
in commit
                    File
/usr/local/opt/Zope/server/test2/lib/python/ZODB/Transaction.py, line
208, in commit
                  TransactionError: A serious error, which was probably
a system error,
                                  occurred in a previous database
transaction.  This
                                  application may be in an invalid state
and must be
                                  restarted before database updates can
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 until
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´s 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 )