josef, please do not send HTML-formatted mail to this list. currently there is no workaround for the problem you describe. when you hit the "undo" tab the database is scanned for undoable transactions for that particular object and its children, and depending on when things were changed the scan has to go mor or less far into the database to show the number of records that page can display at once. while this scanning is done the ZODB is not available for other requests. and will queue them. if the scan takes a long time some browsers may time out. jens On Tuesday, August 13, 2002, at 06:58 , Josef Meile wrote:

Hi,

 

since I installed the newest-stable Zope version (2.5.1) under Linux Susse

7.3, I have had problemswhen I click on the "undo" tab of the "manage

interface". Sometimesit takes a long time to show me all the transactions

that I can undo.

 

On the while, it blocks Zope. So, people who is visiting the site can't

see it till this is done. Often they will see the common errormessage

that browsers show when they can't load the page.

 

Is there any way of solve this problem? What are the causes?

Thanks in advanced,

Josef.

Josef Meile wrote:

7.3, I have had problems when I click on the "undo" tab of the "manage

interface". Sometimes it takes a long time to show me all the transactions

that I can undo.

Indeed. The undo tabs searches back through the ZODb until it has enough transactions to fill one page. If you have a big ZODB with a lot of revisions, this can be excutiating :-S

On the while, it blocks Zope. So, people who is visiting the site can't

see it till this is done. Often they will see the common error message

that browsers show when they can't load the page.

Indeed...

Is there any way of solve this problem? What are the causes?

Packing the ZODB will help, but Undo will always behave like this, so I can't really suggest much else... cheers, Chris