Am 27.11.2012 um 14:39 schrieb exar...@twistedmatrix.com:
>> The only reason I’d prefer to stay with pooling is that I very much
>> expect the traffic to rise and wouldn’t really want to change away and
>> go back later. :(
> Then I'd strongly recommend taking a look at twext.enterprise:
>
> h
On 27/11/12 12:49, Hynek Schlawack wrote:
> Yep, and the connections *do* heal after dying. I don't have to restart
> twistd, it just takes a few failed requests to warm up again.
Yes - one attempt per thread in the pool.
It is a pain. But as per recent discussions on the list, there's no
conse
On 12:49 pm, h...@ox.cx wrote:
>
>The only reason I’d prefer to stay with pooling is that I very much
>expect the traffic to rise and wouldn’t really want to change away and
>go back later. :(
Then I'd strongly recommend taking a look at twext.enterprise:
http://trac.calendarserver.org/browser/
> I have a really bad time with the combination of a low-volume service and
> adbapi.ConnectionPool, pyodbc, FreeTDS and Sybase.
>
> Basically my connections just time out and fail in weird, generic ways like:
>
> Error: ('01000', '[01000] [FreeTDS][SQL Server]Unexpected EOF from the server
>
On Tue, Nov 27, 2012 at 4:16 AM, Hynek Schlawack wrote:
> Hi,
>
> I have a really bad time with the combination of a low-volume service and
> adbapi.ConnectionPool, pyodbc, FreeTDS and Sybase.
>
> Basically my connections just time out and fail in weird, generic ways
> like:
>
> Error: ('01000',
Hi,
I have a really bad time with the combination of a low-volume service and
adbapi.ConnectionPool, pyodbc, FreeTDS and Sybase.
Basically my connections just time out and fail in weird, generic ways like:
Error: ('01000', '[01000] [FreeTDS][SQL Server]Unexpected EOF from the server
(20017) (
