Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125])
	by mail.postgresql.org (Postfix) with ESMTP id 5BC091B05A0F
	for <pgsql-jdbc@postgresql.org>; Thu, 15 Dec 2011 23:57:39 -0400 (AST)
Received: from mail-qw0-f46.google.com ([209.85.216.46])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ringerc@ringerc.id.au>) id 1RbOvP-00081F-1N
	for pgsql-jdbc@postgresql.org; Fri, 16 Dec 2011 03:57:39 +0000
Received: by qadc12 with SMTP id c12so714609qad.19
	for <pgsql-jdbc@postgresql.org>; Thu, 15 Dec 2011 19:57:21 -0800 (PST)
Received: by 10.224.177.16 with SMTP id bg16mr9608145qab.7.1324007841626;
	Thu, 15 Dec 2011 19:57:21 -0800 (PST)
Received: from [10.1.1.6] (124-169-254-28.dyn.iinet.net.au. [124.169.254.28])
	by mx.google.com with ESMTPS id
	dj8sm16975477qab.19.2011.12.15.19.57.17 (version=SSLv3 cipher=OTHER);
	Thu, 15 Dec 2011 19:57:20 -0800 (PST)
Message-ID: <4EEAC19A.30806@ringerc.id.au>
Date: Fri, 16 Dec 2011 11:57:14 +0800
From: Craig Ringer <ringerc@ringerc.id.au>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Dave Cramer <pg@fastcrypt.com>
CC: =?UTF-8?B?UmFkb3PFgmF3IFNtb2d1cmE=?= <rsmogura@softperience.eu>,
	David Fetter <david@fetter.org>,
	Sylvain Mougenot <smougenot@sqli.com>, pgsql-jdbc@postgresql.org
Subject: Re: Re: [SQL] JDBC Statement.setQueryTimeout : is there plan
	to implement this?
References: 
 <CACKdPFjK_UsZ5wExD-RvBbvi6Zo-VYtoxQsCUpWXzTN9kywj7w@mail.gmail.com>
	<4EE8AC41.2040505@ringerc.id.au>
	<20111214161349.GA31176@fetter.org>
	<4EE968FF.5010604@ringerc.id.au> <4EE97B85.50909@ringerc.id.au>
	<c138137e3524335c64e646b0e88e7dbc@mail.softperience.eu>
	<4EE9FE03.7070107@ringerc.id.au>
	<CADK3HHJmo4ayR=RKBeomggu48=tbGYV7HdX7FVP_QOoFt=du+Q@mail.gmail.com>
In-Reply-To: 
 <CADK3HHJmo4ayR=RKBeomggu48=tbGYV7HdX7FVP_QOoFt=du+Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -1.2 (-)
X-Archive-Number: 201112/67
X-Sequence-Number: 22521

On 15/12/2011 10:17 PM, Dave Cramer wrote:
> Craig,
>
> That is the current implementation. What do you suggest as a more
> robust implementation ?

A java.util.concurrent.ScheduledThreadPoolExecutor

http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/package-summary.html

See discussion: 
http://stackoverflow.com/questions/8514725/obtaining-a-java-util-timer-or-equivalent-in-a-javaee-friendly-way-that-works-on

I'd just skip building statementTimeout support for the JDBC3 driver, 
avoiding the issue with the JDK 1.5 requirement that way.

--
Craig Ringer