Pletli Antal wrote at 2006-9-21 09:12 +0200: > ... >I use the same product. >This problem is one of the others...
I had to fix a problem in "psycopg": During "connect", Python's Global Interpreter Lock (GIL) was not released (freezing Zope during connect). Usually, this is not a problem as "connect" is quite a fast operation. We noticed it only when the server for the postgres installation was down (then "connect" became a several minute operation until the TCP timeout happened). However, it is unlikely, that this is your problem. >The behaviour is the same when i >use long socket communication (as a tcp client), etc. This, too, should not happen -- and I never observed it (but a colleague reported something like this but never showed it to me -- and I did not believe him; or more precisly, I tested his alledgedly observed behaviour and could not reproduce it...) >In these cases the >folder wich contains the scripts be unaccessible. Unbelievable -- unless your folder access triggers the long socket communication. In this case, it would not be the old socket communication that "blocks" but the new one. Of course, your folder access should not trigger anything else... -- Dieter _______________________________________________ Zope maillist - [email protected] http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
