db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: Bug with query timeout
Date Sat, 10 Sep 2005 07:31:15 GMT
Daniel John Debrunner <djd@debrunners.com> writes:

> I think I just noticed an bug with the new query timeout function, I
> should have seen it during the review.
>
> The timeout is being set on the class GenericPreparedStatement, but this
> represents a statement plan and can be shared across multiple
> connections (through the statement cache). Thus if two connections
> execute the same statement with different timeouts, they will interfere
> with each other with the timeout values.
>
> I think the solution is to pass the timeout into the execute method of
> org.apache.derby.iapi.sql.PreparedStatement, not store it as a field in
> GenericPreparedStatement.

I don't know if it is related, but when I ran derbyall yesterday
SetQueryTimeoutTest didn't terminate.

-- 
Knut Anders

Mime
View raw message