Received: by 10.52.67.209 with SMTP id p17mr4581604vdt.0.1331157389560;
        Wed, 07 Mar 2012 13:56:29 -0800 (PST)
X-BeenThere: rails-sqlserver-adapter@googlegroups.com
Received: by 10.52.170.78 with SMTP id ak14ls2738248vdc.6.gmail; Wed, 07 Mar
 2012 13:56:28 -0800 (PST)
Received: by 10.52.20.173 with SMTP id o13mr4568538vde.1.1331157388858;
        Wed, 07 Mar 2012 13:56:28 -0800 (PST)
Received: by 10.52.20.173 with SMTP id o13mr4568537vde.1.1331157388847;
        Wed, 07 Mar 2012 13:56:28 -0800 (PST)
Return-Path: <k...@actionmoniker.com>
Received: from mail-vx0-f169.google.com (mail-vx0-f169.google.com [209.85.220.169])
        by gmr-mx.google.com with ESMTPS id hc9si4205434vdb.2.2012.03.07.13.56.28
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 07 Mar 2012 13:56:28 -0800 (PST)
Received-SPF: pass (google.com: domain of k...@actionmoniker.com designates 209.85.220.169 as permitted sender) client-ip=209.85.220.169;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of k...@actionmoniker.com designates 209.85.220.169 as permitted sender) smtp.mail=...@actionmoniker.com
Received: by vcbfk14 with SMTP id fk14so6822798vcb.0
        for <rails-sqlserver-adapter@googlegroups.com>; Wed, 07 Mar 2012 13:56:28 -0800 (PST)
Received: by 10.52.36.176 with SMTP id r16mr5973373vdj.84.1331157388426;
        Wed, 07 Mar 2012 13:56:28 -0800 (PST)
Return-Path: <k...@actionmoniker.com>
Received: from station.actionmoniker.com (gateway.actionmoniker.com. [70.169.150.166])
        by mx.google.com with ESMTPS id e10sm38608725vdj.21.2012.03.07.13.56.26
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 07 Mar 2012 13:56:27 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: [RailsSQLServer] Connections handling
From: Ken Collins <k...@metaskills.net>
In-Reply-To: <E4D36E1C-70C9-4E12-AB74-97E1EA65712D@gmail.com>
Date: Wed, 7 Mar 2012 16:56:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5E96B11-113A-42B7-ABB6-B144F4EEA...@metaskills.net>
References: <13280802.2046.1331146979263.JavaMail.geo-discussion-forums@vbbfy7> <E4D36E1C-70C9-4E12-AB74-97E1EA657...@gmail.com>
To: rails-sqlserver-adapter@googlegroups.com
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQkU8GnV8Xvl1kWUJKRqKLgU/lHEd77JwB2WRAliXAhXq0TJog3D40Rgu7gN/mO22s6BQbdi


We have some tests in TinyTDS for this. In general we return INT_CANCEL =
for the server down message so we can keep on trucking.=20

=
https://github.com/rails-sqlserver/tiny_tds/blob/master/ext/tiny_tds/clien=
t.c#L57

This is supposed to compliment the adapters connection handling too by =
checking the state of the connection and dropping it if needed and =
creating a new one. Here lately I have been appending this info I =
recently found on the bottom of connection related issues. It covers =
keep alive settings and may be useful.

http://blogs.msdn.com/b/sql_protocols/archive/2006/03/09/546852.aspx

    It causes good connection to break during transient network =
failures.=20
    So configuring the keep-alive values too small is not recommended


On Mar 7, 2012, at 3:33 PM, Clifford Heath wrote:

> Just off the top of my head, it sounds like FreeTDS might not be =
rigorously checking for errors on the socket.
> If this results in it writing on a socket that's been closed, it can =
result in a signal that will kill the app.
>=20
> Try adding a catcher for SIGPIPE and see if it gets called.