[egenix-users] Re: [Zope-DB] mxODBC connection to SQL Server 2000 freezes Zope

[M.-A. Lemburg]

Tim Edwards wrote:
> We are using the FreeTDS v0.61 driver to connect unixODBC to the SQL Server
> database. We are running select, update and delete queries - not nested,
> just simple queries. The problem seems to occur when we have more than one
> egenix mxODBC connection object open at a time. 
> 
> Using the Zope management interface I have tried opening more than one
> connection at a time. When I do this the Zope server becomes unresponsive
> (as described below in 1st email) and then returns to normal after 10-15
> seconds. However the connection that I tried to open is closed. If I close
> all connections and then try to open one it works fine. If I then try to
> open another it does this.
> 
> Any help greatly appreciated

This sounds like a problem with the FreeTDS driver. Please try
out the 1.0.7 beta I posted yesterday and see if it helps. We've
made the connection pooling a bit more restrictive and that
should help drivers that are not 100% thread safe.

> -----Original Message-----
> From: M.-A. Lemburg [mailto:mal at lemburg.com]
> Sent: Saturday, 8 November 2003 10:21 PM
> To: Tim Edwards
> Cc: 'egenix-users at lists.egenix.com'; 'zope-db at zope.org'
> Subject: [egenix-users] Re: [Zope-DB] mxODBC connection to SQL Server
> 2000 freezes Zope
> 
> 
> Tim Edwards wrote:
> 
>>Hi,
>>
>>We are using mxODBC 1.0.6 to connect to a MS SQL Server 2000 server from
>>Zope 2.6.1 running on a Red Hat Linux 8 server. The problem is that the
>>database connection sometimes freezes the Zope instance.
> 
> 
> Can you provide more background information about the kinds of
> queries you are running ? It is also important to know about
> the ODBC driver you are using to access MS SQL Server from
> Linux.
> 
> 
>>When this occurs it
>>becomes difficult to access the Zope management interface - we keep
> 
> getting
> 
>>'Cannot Find Server' messages in the frames, with it only loading a frame
>>correctly on every 2nd or 3rd refresh. Once we manage to get into the
> 
> folder
> 
>>that has the database connection and click the 'Close Connection' button
> 
> on
> 
>>the status page Zope returns to normal. 
>>
>>Has anyone experienced problems like this?
>>
>>The following was pasted from the Status page of the connection:
>>Connection Options 
>>*	Database Warnings are reported as Python exceptions. 
>>*	Connection uses auto-commit. 
>>*	Time columns are returned as DateTime values. 
>>*	Date/time columns are returned as Zope DateTime values. 
>>*	Short integers are fetched as short integers. 
>>*	Scale 0 floats are converted to integers. 
>>*	The first available result set is fetched in queries. 
>>Connection Pool Pool size: 1 
>>Physical connections: 0 open 
> 
> 

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Software directly from the Source  (#1, Nov 10 2003)
 >>> Python/Zope Products & Consulting ...         http://www.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::