To rule out the DCO2 code itself perhaps you could add a time.sleep(..) call right before the Oracle call is actually made. This sleep should also not block other threads, but will verify that no other Python level locking is occuring. Just a thought, John On Wednesday 15 August 2001 11:52, Matthew T. Kromer wrote:

Rasmus Bording wrote:

...

hey!

Our Zope application "blocks" when it uses the DCO2 connection to our Oracle database. I.e. Zope wont handle other requests until the Oracle query has finished. Anyone got a clue why?

We are using DCO2 beta5 and Zope-2.3.0 on Linux.

Thanks. Rasmus Bording

Hi,

That's interesting -- It shouldn't block, but that doesn't mean it isn't, obviously. You are running Zope with more than one thread, I'm sure. Each long-running operation in DCOracle2 will yield the global interpreter lock to allow other threads to run, so it could be that something else is causing the blockage.

Do you have a simplified example you can use to demonstrate this? I may try to reproduce it with an enormous join, I don't have much experience at making Oracle run *slowly* ;)

_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )

-- . . . . . . . . . . . . . . . . . . . . . . . . John D. Heintz | Senior Engineer 1016 La Posada Dr. | Suite 240 | Austin TX 78752 T 512.633.1198 | jheintz@isogen.com w w w . d a t a c h a n n e l . c o m