Re: a problem about setQueryTimeout is not fixed?

Tomonari,

I don't have a problem putting this up on the site as the latest driver.

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

On Tue, Jul 16, 2013 at 4:57 AM, Tomonari Katsumata <
katsumata(dot)tomonari(at)po(dot)ntts(dot)co(dot)jp> wrote:

> Hi Dave,
>
> I've tested the new driver(postgresql-9.2-1004.**jdbc4.jar).
> It worked fine.
>
> My test scenario:
> step0. preparing tomcat connection pool environment.
> step1. connect to PostgreSQL with pooled connection.
> step2. executing setQueryTimeout(5).
> step3. executing dummy query(access to non exist table) and get
> SQLException.
> step4. cotinueously, executing "SELECT pg_sleep(10)".
>
> the result:
> - old driver
> getting SQLException during step4.
> because of timer expired from step2.
>
> - new driver
> query of step4 complete without any error.
>
>
> I'm happy to the new driver be released soon,
> but I'm concerning about a quick release make
> many users chaos.
>
> Now, you are working for website renewal, rigth?
> So, I think it's better to release new driver on
> renewal websit.
> What do you think of it ?
>
> regards,
>
> --------
> NTT Software Corporation
> Tomonari Katsumata
>
>
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/**mailpref/pgsql-jdbc<http://www.postgresql.org/mailpref/pgsql-jdbc>
>