RE: [Zope] Problem with running same script at a time
Hi Dieter! Than you for your answer! I use the same product. This problem is one of the others... The behaviour is the same when i use long socket communication (as a tcp client), etc. In these cases the folder wich contains the scripts be unaccessible. Maybe have i a wrong zope configuration (i use default config)? Antal -----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de] Sent: Wednesday, September 20, 2006 9:40 PM To: Pletli Antal Cc: zope@zope.org Subject: Re: [Zope] Problem with running same script at a time Pletli Antal wrote at 2006-9-20 14:48 +0200:
I have experienced that when i run a python srcipt (it is a long postresql query) from a user folder then i cannot access this folder from management form while the process is running. If i try at the same time to run this script again the process will start after the other one ends. Other folder are accessible. What do i wrong?
This is surprising... You might be using an unfortunate Postgres adapter library. We are using "psycopg" and do not observe this problem. -- Dieter
--On 21. September 2006 09:12:47 +0200 Pletli Antal <a.pletli@euromacc.hu> wrote:
Hi Dieter!
Than you for your answer! I use the same product. This problem is one of the others... The behaviour is the same when i use long socket communication (as a tcp client), etc. In these cases the folder wich contains the scripts be unaccessible. Maybe have i a wrong zope configuration (i use default config)?
Perhaps you're other worker threads are blocked by long-running requests? -aj
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
participants (3)
-
Andreas Jung -
Dieter Maurer -
Pletli Antal