Mailing-List: contact user-help@thrift.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@thrift.apache.org
Received-SPF: pass (athena.apache.org: domain of dan.kuebrich@gmail.com
 designates 209.85.212.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4FDA30BB.1080500@subwest.com>
References: <4FDA30BB.1080500@subwest.com>
From: Dan Kuebrich <dan.kuebrich@gmail.com>
Date: Thu, 14 Jun 2012 15:06:01 -0400
Message-ID: 
 <CAEExJ=yHA4q4kD4Zb=rPRe8wgaYe6uv-0akUpJe6ssWVRE6ZQg@mail.gmail.com>
Subject: Re: Python - Killing an active Thrift call
To: user@thrift.apache.org
Content-Type: multipart/alternative; boundary=f46d0442844e315d4004c27365a2

--f46d0442844e315d4004c27365a2
Content-Type: text/plain; charset=ISO-8859-1

I don't know that there's a built-in facility for this, but it sounds like
what timeouts are often used for.  How are you receiving the info that the
other side won't return? Can you use timeouts on the thrift client sockets
for this?

On Thu, Jun 14, 2012 at 2:43 PM, Steve <steve@subwest.com> wrote:

> Hi,
>
> Is it possible to kill an active/open request in Python?
>
> I have locking code around a thrift call, but sometimes the other side
> (server) doesn't return (not in my control).  I would like to force that
> connection to close so that the thread can continue on.
>
> I've tried to close the transport, thinking it would fail out, but no luck.
>
> Thanks.
>
>

--f46d0442844e315d4004c27365a2--