Daniel John Debrunner <[EMAIL PROTECTED]> 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
